On Wed, 27 Jun 2001, Stefan Seefeld wrote:
> precisely, you are making my point.
Good then, I wasn't sure what your point was :-) I thought you were
suggesting some sort of table of predefined strings, one per known
device, which would be in a header file such that e.g.
GII_DEVTYPE_POWERGLOVE could be used to find the string "PowerGlove";
Which would be a horrible way to do it.
> > Now, an app that wanted to know the version, would call an API
> > function giiExtractVersion(str) to get the version string out. Versions,
> > BTW have to be strings because not everyone uses the same notations.
> > If we cleverly choose the format of the string, we should be able to
> > make escape characters rarely needed.
>
> and why do you want to force everything into a single string that then has to
> be parsed to get back to the original tokens ?
Why do you want apps to have to find a bunch of fields and assemble them
themselves?
Anyway, six of one, half dozen of the other, I'd be happy with either, but
I think we should create the structure such that any string pointers
point into the same allocated block. I have suspicions about the libgii
code that that will be easier to implement.
> sure. Strings are null terminated, and the dictionary itself is, too.
> Nothing special about that. A cleanup handler is easily written.
Don't need one if we use an incestuous structure.
--
Brian
