pointers
I can think of 2 cases where pointer would be helpful
for me.
1: Conversion of languages such as C & Pascal
2: Accessing of 1D sequences such as {1, 2, 3, 4, 255, 0}.
I could use it to copy 1D sequences to video memory.
I could use it to create masks using the sequence
operators such as and_bits. This would keep me from
having to peek() and poke() to do operations on
sequences in memory.
I realize that Multi-Dimensional Sequences can't be supported.
I also realize that the 1D sequence would not be allowed to
be altered in size AND that the 1D sequences could only contain
values from 0 to 255. These values are bytes. All other values
are multiple bytes and MUST be represented differently.
What I ask seems simple from MY stand point BUT.
I don't know how the structure of sequences is handle.
I don't know if the information for sequences is hanlded with
header type information OR some sort of Multiple header type.
If there is one header at the very begining of the sequence then
there shouldn't be any problem.
BUT if there are little headers maintained through out the
sequence structure then that would quickly and easily corrupt
the sequence.
As You see Robert.
I fully understand the Possible complications
involved with pointers to sequences.
I can also see where there could be complications involving
atoms, and integers.
objects would be simply impossible.
Another problem I just thought of is his dynamics for saving
space in sequences.
<CODE>
sequence s1, s2
s1 = {1, 2, 3, 4}
s2 = s1
<CODE>
s2 is only pointing to s1 so pointing to s2 and then
changing s1 would corrupt the pointing.
All of these problems can be overcome but they Might take
a lot more effort than others realize or relized before this
message.
Sincerely, Lucius L. Hilley III
A thrilled little Euphoria programmer.
--Lucius Lamar Hilley III
-- E-mail at luciuslhilleyiii at juno.com
-- I support transferring of files less than 60K.
-- I can Decode both UU and Base64 format.
|
Not Categorized, Please Help
|
|
