OpenEuphoria

Re: implications, flames, etc.

• Posted by Mark Brown <mabrown at SENET.COM.AU> Feb 02, 2000
• 617 views

-----Original Message-----
From: Everett Williams <rett at GVTC.COM>
To: EUPHORIA at LISTSERV.MUOHIO.EDU <EUPHORIA at LISTSERV.MUOHIO.EDU>
Date: Wednesday, February 02, 2000 12:38 PM
Subject: Re: implications, flames, etc.


Hi Everett


> In general, I'd like
>to have straightforward access to anything that can be called in the most
>general sense of that word. That requires two things the ability to
reasonably
>describe the data to be sent and received without peeking and poking
>everything(structures) and a more generalized and flexible calling
procedure.
>


I'm a Euphoria newbie but have already found frustration in not being able
to get at the location of my variables. I wouldn't want to know for my own
code but so much of what I  want to call expects me to know where that
variable is. I'm not even particularly concerned on performance grounds (EU
seems to hum along quite nicely). It just makes doing something simple so
untidy. I know Rob is opposed to this (I can understand that he does not
want the competition to get at his language) but as the language grows,
people (even incompetents like me) are going to want to do odd things.

Cheers.

Mark