std library hooks
Nick Sabalausky
SeeWebsiteToContactMe at semitwist.com
Sun Apr 15 21:49:18 PDT 2012
"Walter Bright" <newshound2 at digitalmars.com> wrote in message
news:jmfqhq$6cu$1 at digitalmars.com...
> On 4/15/2012 5:27 PM, Sean Kelly wrote:
>> If you're overriding the one in the library then it has to be documented
>> to
>> have that name. It also has to live in its own section or you can have
>> link
>> errors.
>
> Yes, that is correct.
>
>> By comparison, hooks for commonly overridden things seems a bit
>> easier.
>
> I don't agree. Having a hook means you have to set up a pointer,
Not if it's a compile time hook as I described.
>document it,
That needs to be done anyway. The link-time "hook" system has such horrid
semantics, diagnostics and compatibility, you're gonne need to document the
hell out of that if you expect people to actually use it.
More information about the Digitalmars-d
mailing list