OpenEuphoria

Re: upper()

• Posted by "Kat" <kat12 at coosahs.net> Aug 11, 2006
• 683 views

> 
> 
> On Thu, 10 Aug 2006 10:34:09 -0700, Hayden McKay
> <guest at RapidEuphoria.com> wrote:
> 
> >}}}
<eucode>
> >global function upper(sequence st)
> >    asciiLUT = euinc:upper(asciiLUT)
> >    ...
> >end function
> >
> >global function lower(sequence st)
> >    asciiLUT = euinc:lower(asciiLUT)
> >    ...
> >end function
> ></eucode>
{{{

> Ouch! You clearly don't need to call euinc:lower/upper every single
> time these replacements are called.
> 
> One other thing I feel a need to say here is that it seems apparent
> that this approach will match the usual upper/lower 100%. It will not.
> As a (daft) example, euinc:lower(75.123) will give 107.123 whereas the
> replacement will typecheck on both 75.123 and {75.123}; and, if
> "integer ch" is replaced with "atom ch", the latter will give {107}. 
> 
> No biggie, just saying don't claim/think 100% compatible when not. I
> am of course slighting wildcard.e on that last point, not your code.
> 
> Barring those niggles, I think that is a clever approach.

I have been using the code Derek supplied, and run times have 
been ~6 sec to ~140 seconds, depending on how busy the 
machine is. 

This has all become academic. The neighbor's new dogs have been 
challenging me for right to access my property and mailbox, and 
the neighbor is now threatening to sue me for harrassment even tho 
i have constantly tried to avoid him. I'll be living in my car, in other 
states, after court on August 15th 2006. This is the only way i 
know to get further away from him and his dogs.

Kat