When I load TCC, there are at least 60 different .dll files that get loaded,
and I don't want to know about any of them. Of those files, only Say.dll
announces itself. Your plugin very nicely responds to @VERINFO[Say.dll] if I
want to know what version it is. (BTW: None of my other plugin .dll files do
respond to that.)
This is of course my opinion only. Beggars can't be choosers, but I wanted
to at least express my opinion about the interface. Still, I stand by the
opinion that using a system wide environment variable of that generic a name
is inappropriate. I've been stung too many times myself by poor name choice
and am now sensitive to it.
On Wed, Jun 9, 2010 at 9:29 AM, Charles Dye <> wrote:
> ---Quote (Originally by Jim Cook)---
> I think "noloadmsg" is much too generic a name and doesn't imply anything,
> let alone a SAY plugin for TCC.
> ---End Quote---
> It's deliberately generic; the same variable works in all of my plugins. I
> can't imagine why you would want to disable the startup message in one, but
> not in another. (Actually, I can't imagine why you'd want to disable it at
> all, but apparently some folks do.)
>
>
> ---Quote---
> Can a plugin be sensitive to its own name at load time? What if say.dll
> displayed a banner, but sayquiet.dll did not, or something like that.
> ---End Quote---
> It could, but that would involve adding code. Checking an environment
> variable was a zero-line fix, since I'm doing an ExpandVariables() there
> anyway.
>
>
>
>
>
--
Jim Cook
2010 Sundays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Monday.