Re: address of variable
Kat wrote:
>> >
>> Sounds like an admission that Euphoria as it now stands is unable
>> to deal cleanly with things such as I have described above. It might be
>> noted that routine_id implements a pointer that is then passed as a value.
>> So much for consistency. Must be terrible when the real world intrudes.
>
>Everett, you gotta know that when an atom in a sequence takes up 4 bytes
>that 3 of those bytes have important data about the other byte's place in
>the world,,, and you shouldn't mess with those 3 bytes. Eu has more than one
>poke(), is there something besides that ( and the things i mentioned above )
>that you wish to do?
>
>Kat
Actually, I was following my license and not checking such things...not that
I doubt what you are saying. But thanks for making my point. A quick look
at the DBF-eng code from the archive will show you what absolute gyrations
one must go to, to deal with externally formatted data. This only deals with
DBF III files. A few simple structures could get rid of about 90% of that
code. I'm not asking for access to those precious internal formats. I'm
asking for some way to deal with structured external data without doing
things that relate only to Euphoria's internal peculiarities. The problem is
on the way out. Unless, the external data is dealt with entirely as meta-data
within Euphoria, it becomes necessary to understand what you are not
supposed to know about it to get it back into an external form. Actually,
not even that will suffice unless one uses poke and it's variants. Every
thing else violates that fact that you aren't supposed "know" about the
internal format of anything. This gets into "the Emperor's new clothes"
type of discussion. Wink, wink..nod, nod..we don't really know what
those internal variables look like. Except the IO routines do "sort of"
without really talking about it...or really documenting it for that matter.
Since there is already a huge amount of nodding and winking going on
in ASCII text handling for strings, I "bought" your argument on that one.
Of course, double byte text will break the "unprintable" out of that.
Structured data has no such equivalent and really can't have if we
really believe the words of our esteemed author. Actually, if you follow
his logic, you really can't have native "Euphoria IO". If variable form is
subject to change, then who could ever know what was written out and
how to read it back in.
Everett L.(Rett) Williams
rett at gvtc.com
|
Not Categorized, Please Help
|
|
