On Tue, 3 Oct 2000, Brian S. Julin wrote:
>
> On Mon, 2 Oct 2000, Christoph Egger wrote:
> > /* allocates sizeof(struct mydata) bytes memory
> > * and set it to the visual
> > * struct mydata can be any kind of a structure
> > */
> > ggiOpenMetaData(vis, sizeof(struct mydata));
>
> The extra parameter is just so more than one layer of library
> can use metadata on the same visual without collision. For simple
> use like you want, we would just add convenience macros to the
> extension header:
[snip]
> If it's a library above the extension level, then you wouldn't use
> "" above, but "3dtk", so that other people could store their own
> data in a visual that was in use by 3dtk (assuming they can get to
> the visual object and 3dtk doesn't sheild it under it's own opaque
> object)
I see. OK. Then an API as you suggested in a previous mail is OK.
> So the remaining question is, is it worth the effort to code?
> How many people would use it, and would their using it make their
> code more, or less, reusable?
Only the list can answer these two questions.
> If you were later to convert some 3dtk functions from a high level library to
> a full extension, would this gum up the process or make it easier?
Easier.
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
