Re: 64bit support
- Posted by Critic Mar 03, 2009
- 1134 views
What's not totally clear from this is that base actually points to the address of postfill, where the data comes after that (which is similar to what you were looking for). So we actually allocate a single, contiguous block of memory.
In this case my suggestion should be simple to implement?
You're right with respect to assembler, but I'm not sure if you're serious.
I just checked if I got your point.
Perl, for instance, is often referred to as a write only language for just this reason.
Well, I think of Perl as a joke. 
No need to argue about Perl, though.
I find that euphoria is high level enough, and the language small enough that it doesn't get in the way of getting a higher level understanding of the code than other languages sometimes do.
I am not sure. In EU structs or objects are simulated with sequences which could be disturbing. "To break a butterfly on a wheel" does not make the code clearer. (Hope I got the saying right.)
Sometimes it relates to static typing, or simply the ease of dealing with sequences.
Python's lists do pretty much the same as sequences. AFAIK EU does not do much static type checking. User-defined types are checked at runtime, if I am not mistaken.
The pass by reference nature of euphoria can cut both ways. If I pass a value to a routine, I know that it won't be modified. Of course, that also means that I can't modify it if I want to.
And it means that procedures/functions cannot be split up in smaller parts easily.
