Jesper . Naur <[EMAIL PROTECTED]> writes:
>Nick Ing-Simmons <[EMAIL PROTECTED]> writes:
>
>> >LANGCLIENTMESSAGE
>> >LANGCMPARG
>> >LANGCMPOPT
>[snip]
>> >These names, including the remaining 109, are all defined in the object
>> >library [-.blib.arch.auto.Tk]TK.OLB, so by modifying [.EVENT]EVENT.OPT to include
>[-.blib.arch.auto.Tk]TK.OLB, it becomes possible to link EVENT.EXE by hand.
>>
>> That is odd - it would seem that your C compiler is creating references
>> to things which are not used. i.e. just an
>>
>> extern foo();
>>
>> Is enough to force need for foo.
>
>This claim is perhaps a bit premature: The C compiler, which I use (DEC C 5.07-004),
>does not do this - a fact I have proved using the following trivial program:
>
>#include <stdio.h>
>extern void NonExistingName ( int variable );
>void main( void )
>{
> printf("exttest\n");
>}
>
>It compiles, links and runs without undefineds.
Hmm,... well that seems to kill that theory.
>
>I have searched the entire Tk800.018 for usages of all the 119 names, and it appears,
>that they are actually all used. The first 3 names are used by the following modules:
(Can you press return occasionally long lines display okay when reading but I can't
see them when composing a reply.)
I know that they are used _somewhere_, but they are NOT all used by Tk::Event.
If I recall correctly we were trying to explain why you needed to link
Tk::Event with pTk/libpTk.a or whatever.
Tk::Event is supposed to be a completely stand-alone module.
It is a place holder for Joshua's Event module.
Thus the core event loop bits of Ptk are supposed to be pulled out
of pTk/libpTk.a or #include'd into .c files in Event and compiled there.
Those routines should _only_ be in Event and not in Tk itself. Likewise
all the GUI stuff should be in Tk and not in Event.
They various routines are all lumped into pTk for historical and
convienience of porting-from-Tcl reasons.
>
>LangClientMessage is used by TKEVENT.C
>
>LangCmpArg is used by TKBUTTON.C and TKMENU.C
>
>LangCmpOpt is used by CHNGLUE.C, TKCLIPBOARD.C, TKCONFIG.C, TKFRAME.C, TKGRAB.C,
>TKGRID.C, TKMENU.C, TKPACK.C, TKPLACE.C, TKSELECT.C, TKTEXT.C, TKTEXTDISP.C and
>TKUNIXSEND.C.
>
>I could go on, but you get the picture.
I know what the picture is supposed to look like ;-)
>
>You write, that they are not used - do I then have problems because I have overlooked
>some mechanism, which excludes certain modules (like the .EXC files, which you told
>me about a year ago) - or are they actually used after all?
Ah - that may be the clue. There are various "exclude this on platfrom xxx"
files. It is possible that VMS has pulled in something it shouldn't.
--
Nick Ing-Simmons
