Randy W. Sims <[EMAIL PROTECTED]> writes:
>
>I agree. Running xsubpp on such a file does nothing but make a copy. The
>module in question is in libwin32. ( Which, along with Tk, seemed like a
>good testbed because they contain alot of XS modules. )
Tk may have a lot of XS modules but is not typical XS code.
Most of Tk's XSUBs are actually hand coded in tkGlue.c etc. and newXS'ed
by hand. Most of the .xs files are trivial and only really exist
to cause load of the associated core tk code.
...
#include "tkGlue.h"
#include "tkGlue.m"
DECLARE_VTABLES;
MODULE = Tk::Entry PACKAGE = Tk
void
entry(...)
CODE:
{
XSRETURN(XSTkCommand(cv,Tk_EntryCmd,items,&ST(0)));
}
PROTOTYPES: DISABLE
BOOT:
{
IMPORT_VTABLES;
/* Lang_TkCommand("entry", Tk_EntryCmd); */
}
There are some more extensive .xs files in Tk - and of course any new scheme
needs to handle nested dirs with XS etc.
My Audio::Data module is "more" traditional XS
>
--
Nick Ing-Simmons
http://www.ni-s.u-net.com/
