On måndag, maj 13, 2002, at 04:09 , Nick Ing-Simmons wrote:
> If you build your non-threaded perl with MULIPLICITY it has a dTHX too. > (Once upon a time accessing PL_xxxx via aTHX was faster than going for > a global - old GCC on a RISC machine - so I have always built that way.) > > I am fairly sure I have executed am Ithreads built Tk on a MULTIPLICTY > perl and vice-versa and had it work - but probably not deliberately. Makes sense, yes MUTLIPLICTY and ITHREADS should be a bit compatible (all get an extra first argument and so on. However all clibrary functions are not going to be reentrant nor we will it use the data from reentr.h. I don't think aiming for binary compatiblity between threaded and non threaded builds is a worthwhile goal. Arthur
