Re: Euphoria features
-----Original Message-----
From: Irv Mullins <irv at ELLIJAY.COM>
To: EUPHORIA at LISTSERV.MUOHIO.EDU <EUPHORIA at LISTSERV.MUOHIO.EDU>
Date: Saturday, November 13, 1999 6:50 AM
Subject: Re: Euphoria features
>From: Everett Williams <rett at GVTC.COM>
>Subject: Re: Euphoria features
><snip Jason's type check routine>
>
>> And how is this type of thing going to describe the umpty hundred bit
>> and
>> byte flags in the average message header, no matter the protocol.
They
>> have to be literally unpacked one by one and then moved into a
different
>> sequence or atom before they can be intelligently maneuvered. And
>> since the data stream is dynamic, and treacherous, I really need for
>> type checking to stay on. Can you spell Methuselah...the guy whose
>> age you will approach while all this gets done.
>
>It appears that at least two people are laboring under a misconception
>of exactly what type() does.
>
>Bear in mind that a type() failure can _only_ cause an immediate abend.
Very
>useful when debugging, but worse than useless in a production program.
>Surely I don't have to explain this further.
>
>If type() could modify the passed parameter according to some rules you
set
>up, e.g: ask the clumsy typist to try again, it would be much more
useful.
>If it were faster, that wouldn't hurt either.
>
>Irv
>
Yes, I do understand that declaring a variable to a user-defined type will
cause the program to crash on error. I do believe that this would be useful
for debugging but not for production-quality programs. I would expect types
to be unnecessary in my code before I called it production-quality! But
types can also be used not for declaring a variable but as a special purpose
function for range testing. And the program doesn't exit when type is used
in that fashion.
__________________________________________
NetZero - Defenders of the Free World
Get your FREE Internet Access and Email at
http://www.netzero.net/download/index.html
|
Not Categorized, Please Help
|
|