RE: Euphoria Language Changes
- Posted by bensler at mail.com Jan 19, 2002
- 394 views
I tend to agree with this. If you want to pass a value through a routine, use a function. HOWEVER, referenced variables for type defines could be quite useful.. We would be able to do parameter formatting, and keep the syntax checking out of our routines.. If I could get assignment on declaration, the slicing shortcut I mentioned in my previous post, trailing comma support for variable declarations(this one I could do without), and referenced variables for type defines, I would gladly pay another $40 or more to have it. That would be enough modifications to warrant commercial distribution I think.. Oh yeah, add support for viewing sliced sequences in the trace facility. Is that part of the source? Or would that comprimise the PD limitations? Chris Shawn Pringle wrote: > Pass by reference in Euphoria? One of the things that has made Euphoria > > different and I think easier is it's pass by value policy. > Before implementors remind me "it is not really pass by value"... I know > > it is copy on write I am refering only to how it looks to the language > definition only not if it actually does memcpy all over the place. > > Basically I like EUPHORIA's behavior the way it is NOW. Nothing is > modified on the right hand side of the assignment operator. Pass > valueable information into any function or procedure and not worry that > data is accidently modified when it shouldn't. It also makes EUPHORIA > an ideal learning language. EUPHOIA objects returned can be of > unlimited size and structure why pass by reference? only to modify > things in place. > > > Regards, > Shawn Pringle > >