Re: A86: Standards
[Prev][Next][Index][Thread]
Re: A86: Standards
At 02:13 PM 9/5/97 -0400, you wrote:
>Dan Eble writes:
>> No, and it's something we should definitely discuss. It would be good to
>> store all data in type $0B variables, so that they don't get confused with
>
>Is there any way of making a program/.86? file automatically this type? (e.g.
>A byte before the name in the .86? file?) If not, how could it be changed or
>created?
>
>> other variables. Each data type should have it's own identifier: maybe a
>> 4-byte name (similar to extensions in DOS) stored within the variable.
>
>?
>You mean, have all the $0B variables have a 4 letter name, or what? I don't
>see the purpose for that. It should be just as easy to have an 8 letter
>name, with possibly a pointer to the name of the program that uses it or a
>brief description...
>
>> Somewhere, perhaps on my web page, we should keep a registry of all the
>> different types of files so that no one will duplicate one and mess
>> something up.
>>
>> First, a format must be decided upon, though.
>
>Definitely. I suggest something like this:
>
>ret ;In case there's any way to run it
>.db <description>,0 ;Description, such as "Chem86 Data File"
>Data:
>
>;Data goes here
>
>
>
>~Stephen Hicks
>
>
Probably all the non-code files (not programs) on the calc should be stored
with $0B type. So then, continuing with the table theme, it could be
something like this:
ret ;so no running of this type of program
.db 0 ;this could be a type byte, such like:
;0 - library (functions, routines)
;1 - game levels
;2 - icons?
;3 - saved games or something liek that
...
whatever data is needed
This protocol could also be changed easily just by adding another type in
the future
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Alan Bailey mailto:bailela@charlie.cns.iit.edu
IRC:Abalone Web:http://www.iit.edu/~bailela/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
References: