Running a pike as a lib inside another could theoretically work if the embedding interface is developed more.
Since the two interpreters would be completely separate, the only way to pass data between them would be through pipes or the shared memory interface, which only can pass strings.
I was basically mentioning it as 'library-like', because I was guessing the current libraries don't need to go to that kind of memory interfacing - although I have no idea how C-libraries can exchange data with Pike, running on another core in any other way than through shared memory. I lack practical knowledge at that point.
I did not have full 'access all variables' in mind; I was suggesting an interface which would define a limited set of variables (say, function arguments and it's return value) which would be transferred (one-way) between the instances. From entry it might put a pike thread on hold, because it depends on output of code which is running on another core. It could however allow other pike threads to run (as long as they don't access that 'mutexed' output variable?). Far from ideal, but possibly a step towards bringing multi-core to pike, if one knows how to use it in pike.
The planned multi-cpu support aims a lot higher than that. You're welcome to read the preliminary spec here:
http://pike-git.lysator.liu.se/gitweb.cgi?p=pikex.git;a=blob_plain;f=mul ti-cpu.txt;hb=mast/multi-cpu
Feedback is welcome.
It's nice reading, but I'm far from reading it completely yet. I hope we can get there in small steps.
AvS
__________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________