OpenEuphoria

Re: Rob: Q: Euphoria 2.6

• Posted by Jason Gade <jaygade at yahoo.com> Mar 29, 2005
• 466 views

Robert Craig wrote:
> 
> Vincent wrote:
> > Now that Euphoria 2.5 is out, what new features can we look foward to
> > in Euphoria 2.6? Or perhaps you are planning on skipping all the way to
> > 3.0?
> 
> I have a long list of minor issues to look at,
> but I'm still open to suggestions for some major features.
> I may look into threads in more detail.
> 
> Hayden McKay wrote:
> > I'd like to see some structure support for Euphoria since when dealing with
> > the Windows API we need to use structures. Also I would like to see the '^'
> > (carrot symbol) used to define pointers...
> >
> > eg:.. 
> >
> > integer Value
> > ? ^Value -- displays the address of "Value" rather than the value.
> 
> I'm opposed to C-style pointers and structures.
> Programming in a world of values, is fundamentally cleaner
> than programming in a world of storage "locations" that hold values,
> where the values occupy a certain number of bytes in a certain format.
> I would never want to give you the address of a Euphoria variable.
> 
> Regards,
>    Rob Craig
>    Rapid Deployment Software
>    <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
> 

Here we go again, haha!

Better modularity would be nice.  I wouldn't care if it was via an 'import'
keyword or fixing the so-called include bug.  Keeping data and functions in a
module and importing them with a namespace can be very object-oriented-like.

Allow routine id's to be forward referenced.  I've searched the archive for the
arguments against this and I couldn't find them.  All I could find was a note
from Rob saying it was controversial.  Routine id's already get around the normal
function calling process.  Being able to forward reference would be a boon to
writers of large libraries (win32lib).

Those two are the biggest.

I think that people tinkering with the source code and coming with with variable
id's is pretty cool as well.  It is orthogonal with the routine id method.

Being able to modify by reference explicitly, either by variable id or by
in/out/inout declarations.  Or by optimizing the case where foo=somefunc(foo)



=====================================
Too many freaks, not enough circuses.

j.