[Pythonmac-SIG] dynload_next

[Steven Majewski]

On Sun, 27 Jan 2002, Marcel Prastawa wrote:

> NSLINKMODULE_OPTION_PRIVATE breaks VTK. The wrapper is made of a set of
> flat namespace bundles that have undefined symbols (defined in other
> bundles). A global symbol table is needed for this case, the module init
> function does not export C/C++ functions and classes.
>
> Is the PRIVATE flag really necessary? I think we could just keep it
> disabled.

Without the PRIVATE flag, I still get duplicate symbol errors on
trying to import  both time and package.time  bundles.

> > (Also, I believe you used my NSLinkEditError patch, which I'm sorry to say
> >  was very sloppily done for debugging purposes. All those strcat()'s
> >  onto an existing constant string were a big mistake! )
>
> Oh, it was still very useful. I have spent a lot of time doing guesswork
> with the cryptic "Failure linking new module" error message. Maybe we
> could just use a large string buffer and strncat() for now? Some message
> is better than nothing.

The version included in the last post fixes the error reporting -- it
has an external message buffer.

If you define PRIVATE to be 0, it should be functionally equivalent
to your earlier patched code.


-- Steve Majewski