On Sun, 8 Oct 2006 16:58:50 -0700, Eric Wilhelm wrote: Hi Eric
> How about doing this with an external tool (i.e. a utility or Sure, that's OK. > What info will it put in the meta data? I can't say exactly, but I'm thinking that some general principles could be enunciated /and/ followed: o State each condition separately, rather than trying to encode combinations, since we can't say to what future use each will be put. For example, is it reasonable to assume that all external libraries require XS as glue? Even if this is the case, I'd go for all of (fabricating examples here): (1) module_uses_xs: Yes (2) module_uses external_library: Yes or perhaps (2) external_library_language: X (3) language_requiring_compilation: Y o Spell out values, rather than be cryptic or even secretive. So, say Yes/No and not 0/1. For example, XS is cryptic in its own right, in that beginners won't even know WTF XS is, so (1) above, by itself, would be unacceptable to me, In fact it (XS) has implications re compilation that a beginner won't know or even guess. (Thus I always use Yes/No in database fields (disk space is cheap), rather than packing them into a bit, since that way I can dump data without anyone needing to interpret it.) And yes, I'm assuming English here. And the meta data file is small, so a few bytes are nothing. o Don't aim to solve all imagined problems with the first version. Plan for extension of the feature set -- Cheers Ron Savage, [EMAIL PROTECTED] on 9/10/2006 http://savage.net.au/index.html Let the record show: Microsoft is not an Australian company
