karl@grebyn.COM (Karl A. Nyberg) (02/17/88)
[Will there now be a posting on this from somebody named MANFACE at GWU? :-)] The example program given runs with the following (edited) results on Verdix VADS 5.5a (Beta) VAX/ULTRIX. It gives the expected results. Slippage of a tenth of a second between the printing of task A output seems reasonable. Note that when task A gets the CPU, it really GETS the CPU. Right in the middle of printing out a string, task B's output is completely interrupted by task A. This would seem to indicate that pre-emptive scheduling can be supported in the uniprocessor environment. It would also indicate that this compiler is "legal" (in the terms used in a previous posting). -- Karl -- (a.k.a. "whoever") ********TASK A HERE 40371.450 TASK B HERE 40371.470 ... TASK B HERE 40376.460 TASK B HE********TASK A HERE 40376.470 RE 40376.480 ... TASK********TASK A HERE 40381.480 B HERE 40381.490 ... TASK B HERE********TASK A HERE 40386.490 40386.480 ... TASK B HERE********TASK A HERE 40391.500 40391.480