Enki 1.1 Released
Georg Wrede
georg.wrede at nospam.org
Thu Jun 15 02:24:59 PDT 2006
pragma wrote:
> In article <e6ptut$2c61$1 at digitaldaemon.com>, BCS says...
>
>>>> .import("my.import.here");
>>>
>> Are these imports not always needed? Won't any parser use things
>> from these modules? I would think that the basic imports _should_
>> be hard coded (or at least implicitly added to the imports list).
>>
>> On further thought only "enki.types" will _always_ be needed.
>> "enki.BaseParser" will only be used if the default base class is
>> used. But this is detectable, so again, it should be emitted unless
>> the base class is changed.
>
> I'm inclined to agree, but its also at cross-purposes with the
> philosophy I had in mind with the tool. I really think that it
> should try to impose as little as possible, wherever possible. In
> this case, what happens if the user moves or renames 'types.d' to
> something else, or merged the templates in with their base parser?
> I'd rather make imports explicit so the developer has this
> flexibility.
That's what Defaults are for!
More information about the Digitalmars-d-announce
mailing list