Suggestion for Fileman.e
Another Suggestion for Fileman.e
I suggest the following for a future version of fileman.e.
How about using the next 255 bytes after the 255 length bytes,
to indicate the types of the 255 possible fields in the file.
We could let 0 be a Euphoria object, 1 be a sequence, 2
be an atom and 3 be an integer. Then, if other field types
are needed, you could define another 254 of them. I imagine
that would suffice for most purposes. This would allow the
checking of field types both on input and output.
Now, for example, if someone were to create a time or date
field type, they could easily incorporate the code into
Mr. Jackson's routines, or better still, send the code to
Brian and let him test and integrate it into his code. He
could then assign a permanent field type number, which would
be available to all Euphorians!
I know that Dbase stores the names of each field in the header.
This is a possibility and I can see utility here.
Someone discussed the Dbase commands, such as PACK. It seems
to me that the SQL is more common and perhaps easier to
implement?
Larry Gregg
|
Not Categorized, Please Help
|
|
