1. Re: My Lobbying

On Tue, 05 Sep 2000, you wrote:
> My lobbying:
>
> 1.  local variable definitions:
>
>     Just the way they are now except dont generate an error
>     when there is a global with the same name.
>     Locals would be handled as someone else mentioned, like:
>       ThisObject=_Object --access local var
>       ThatObject=Object  --access global var

First of all, you can already declare a variable within a routine
with the same name as a global variable. There are no error messages.
The local is the one that gets referenced.
If we _could_ choose to reference the global variable, it would
be clearer to do it as follows: ThisObject = global Object,
rather than the hard to see and harder to debug _.

> 2a.  External Euphoria structure passing:
>       passing the address of, say, a sequence to another Euphoria
>       program.  The other program gets to operate on the same data.

Can't do. Sequence move around in memory all the time (garbage collection)

> 2b.  Ideally, publish the structure of the sequence along with that
>       to allow true C extensions to the language.  This would allow
>       the greatest boost to Euphoria as programmers could no longer
>       complain they cant do this and they cant do that, and this is
>       too slow and that is too slow.

Wouldn't help, even If we knew the structure, since we can't find it.

> 3a.  if defined, if not defined:
>       this is wayyyy too handy to overlook.
>       Someone else mentioned they like this also.

But why?

> 3b.   Alternately, at least:
>       include ( {thisfile.e, thatfile.e, thisotherfiletoo.e})
>       --wont take much to do that smile
>       That way includes could be conditional.

if x then include .....
else include...
might have some use.

Regards,
Irv

new topic     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu