On 15-06-08 01:15 PM, Lou Burnard wrote:
If we are to abide by Martin's eminently suggestion
You cunningly left the adjective for the reader to supply there, but I don't think we have any option here, do we? We have to deprecate anything we're going to remove for a period of two years, as Syd reminded me recently wrt the defaultVals.
of permitting the new pure odd dataRef to coexist with the current <dataype> mechanism, I can't see any way out of doing the following
I don't think I was suggesting that <datatype> and <dataRef> both be available in a Pure ODD structure, was I? I think I would have meant that the old mechanisms will have to continue to be supported almost indefinitely, but within Pure ODD structures it would be better to use only Pure ODD elements. Nevertheless, I think your three things below are still necessary.
a) make a set of new <dataSpec> elements corresponding with the existing <macroSpec type="dt">s
Makes sense to me.
b) since @ident values are supposed to be unique, these new things will all have to have different names (I suggest teidata.foo rather than data.foo)
Also nice and clear.
c) the current section 1.4.2 on datatype macros (#DTYPES, in #ST) will also need to be cloned, or substantially revised, since this is where the pesky things are actually defined
The chapter prose would have to be expanded anyway, wouldn't it? Cheers, Martin
Anyone got any better ideas?