At 5:58 PM +0100 1/16/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> 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.
Takers wanted. Its ma
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 12:15 PM +0100 1/16/04, Leopold Toetsch wrote:
>>op event_after sleep()
> Works as well. (Though we need to change sleep to wait on an event to
> wake up, but that's separate)
I thought so too. Its mainly a workaround until we have all the events
done,
At 12:15 PM +0100 1/16/04, Leopold Toetsch wrote:
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 IN
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) {
The C translates during
