IMHO we need some more information in the ops files: 1) If an INT argument refers to a label/branch destination 2) For the event-checking code 3) For the safe run core
ad 1) e.g. inline op eq(in INT, in INT, inconst INT) { inline op eq(in INT, in INT, in_branch_const INT) {
Works, go for it.
ad 2) e.g.
op event invoke()
op event_after sleep()
would mean to check at or after that opcode, if events are to be handled. This would be a flag (or 2) in the op_info.
Works as well. (Though we need to change sleep to wait on an event to wake up, but that's separate)
ad 3)
The safe run-core will very likely need to disallow opcodes per category similar as in "perldoc Opcode".
Yep.
I'd also like to have the ability to add in some other parameters to the ops file, so if when we're digging in we could wedge in callouts that by default are ignored, that'd be great.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
