23 Feb
2004
23 Feb
'04
5:10 p.m.
Another restriction would be no multiplicity, i.e. only one pike interpreter per process.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2004-02-23 16:51: Subject: Embedding Pike into C/C++ game
I think the biggest problem is that no one is making a list of the actual problems that should be solved. To me it (since I know so little about the backend, memory management etc) it feels like it shouldn't be that hard to add pike_init and pike_exit that does what main does and then begin to call Pike code (possibly with a set of restrictions like no threads and no call_outs).
/ Martin Nilsson (saturator)