Evolution of Euphoria

new topic     » topic index » view thread      » older message » newer message

Forked from Re: Euphoria's strengths

dcuny said...

What attracted me to Euphoria is a bit different:

  1. Fast enough
  2. Interpreted
  3. Can easily be bound to create a single executable
  4. Simple to use dynamic data structure
  5. No need for prototype files (like .h in C)

However, it seemed that many users were quite hostile to new ideas. There was an attitude that people were guarding the one true language from corruption.

That hasn't really changed.

- David

I have got the impression more than once that the other devs were trying to make EUPHORIA into Perl with a syntax more like Pascal. Most notable is the tendency to want to change the behavior of builtins that had acted a certain way for many years. Take, object(), and bit-wise operations, and now subscript opts. All changed.

The admins of any project determine which feature is a better approximation of the ideal and which are "corruption".

For example, one might say that or_bits should return positive integers because such is more intuitive. This interprets the bits as an unsigned integer. Others might say, because or_bits is a low level routine it should simply be as efficient as possible and return the bits as a signed integer.

S Pringle

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu