1. Eu 2.5 last minute suggestion
I don't know if this is on your list, as I'm sure it has been brought up before.
My guess is that it would be easy to implement, so maybe it is not too late: the
ability to get & use routine_ids for built-in routines would be nice (and
logical).
2. Re: Eu 2.5 last minute suggestion
>
>
>posted by: Andy Serpa <ac at onehorseshy.com>
>
>I don't know if this is on your list, as I'm sure it has been brought up
>before. My guess is that it would be easy to implement, so maybe it is
>not too late: the ability to get & use routine_ids for built-in routines
>would be nice (and logical).
I got one too!!!!
I really like Matt's idea of variable_ids. Could you implement this?
The other thing that would be neat is a function that gets the address of a
Euphoria ATOM in memory (I realize that doing such with sequences would be
way too difficult) Anyway, this function would also ensure that the given
atom takes up x bytes. So:
atom x, MyVariableName
MyVariableName=12345
x=var_id("MyVariableName",4) -- force it to take up 4 bytes of memory from
now on
c_proc(someCprocedure,{x})
William Heimbigner
icxcnika at hotpop.com
P.S. there are more suggestions for Euphoria which can be found on the
UBoard: http://uboard.proboards32.com
FORCEFUL SIGNUPS on the UBOARD have been REMOVED!!!!
3. Re: Eu 2.5 last minute suggestion
On 26 Aug 2004, at 13:54, William Heimbigner wrote:
>
>
> >posted by: Andy Serpa <ac at onehorseshy.com>
> >
> >I don't know if this is on your list, as I'm sure it has been brought up
> >before. My guess is that it would be easy to implement, so maybe it is
> >not too late: the ability to get & use routine_ids for built-in routines
> >would be nice (and logical).
>
> I got one too!!!!
> I really like Matt's idea of variable_ids.
I think i asked for that back about 1999-2000? I asked for the entire mirc var
access: building var names in script, knowing if a var existed, executing vars,
etc. Some of those functions can be done using "associated lists" like Jiri's,
see archives. The "windows server" can be made to do pseudothreads and
string execution.
I've had to make a lot of workarounds, including continuing to use mirc
instead of Eu for some things. Some people here went to Lua, etc.
Kat
4. Re: Eu 2.5 last minute suggestion
Andy Serpa wrote:
>
> I don't know if this is on your list, as I'm sure it has been brought up
> before. My guess
> is that it would be easy to implement, so maybe it is not too late: the
> ability to get
> & use routine_ids for built-in routines would be nice (and logical).
I assume you are familiar with the workaround for this.
-- Make a local wrapper for the built-in.
function my_length(object x)
return length(x)
end function
without warning
-- Make a routine with the same name as the built-in but
-- calls your wrapper.
function length(sequence x)
return my_length(x)
end function
with warning
-- Testing --
integer r_Length
r_Length = routine_id("length")
? call_func(r_Length, {"A string"})
--
Derek Parnell
Melbourne, Australia
5. Re: Eu 2.5 last minute suggestion
Derek Parnell wrote:
>
> Andy Serpa wrote:
> >
> > I don't know if this is on your list, as I'm sure it has been brought up
> > before.
> My guess
> > is that it would be easy to implement, so maybe it is not too late: the
> > ability to
> get
> > & use routine_ids for built-in routines would be nice (and logical).
>
> I assume you are familiar with the workaround for this.
>
> }}}
<eucode>
> -- Make a local wrapper for the built-in.
> function my_length(object x)
> return length(x)
> end function
>
> without warning
> -- Make a routine with the same name as the built-in but
> -- calls your wrapper.
> function length(sequence x)
> return my_length(x)
> end function
> with warning
>
> -- Testing --
> integer r_Length
> r_Length = routine_id("length")
> ? call_func(r_Length, {"A string"})
> </eucode>
{{{
>
Yeah, I've done something like that. I'd love to avoid such workarounds...
