Re: [BLACKBOX] Running command and Wait a second

From: [at]} <Bob>
Date: Tue, 8 Dec 2009 19:33:26 -0000

> Why is it not possible to have both ways?
 
For the same reason that my shoes are not also a shirt!
 
Oberon was designed for single-user workstations in a network. Module.Delay( time ) implies that the operating system can suspend and resume an arbitrary number of pseudo-concurrent processes. That is a reasonable request of an operating system like Unix which was designed for centralised multi-user systems, but it's not what Oberon was intended to do. Retro-fitting would be quite a significant undertaking, I should think.
 
Bob


  _____

From: BlackBox [mailto:BLACKBOX{([at]})nowhere.xy
Sent: 08 December 2009 12:08
To: BLACKBOX{([at]})nowhere.xy
Subject: [BLACKBOX] Running command and Wait a second



Dear BlackBox users,
 
there are always two different ways to look at the same problem.
 
In the old days of Dos programming the application program calls the operating system functions.
At the today’s Windows programming the operating system calls the application program.
 
The new philosophy is: Don't call us! We call you!
 
Who is the boss?
Who is calling?
Is it the BlackBox runtime system or the running command?
Is it possible to have two chiefs?
 
One way is:
   Services.DoLater(func, time);
and the other way will be:
   Xxxxxxxx.Delay(time); or Xxxxxxxx.Wait(time);
And not continue before the time is passed.
 
Which way to prefer depends on the point from where are you looking to that topic.
 
Why is it not possible to have both ways?
How to suspend the running command for a short time and then reschedule that command at the current position?
During the suspend time the background tasks can run.
 
Regards
 
Helmut Zinn
.
 
 
 
 
 
 

---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy

---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy
Received on Tue Dec 08 2009 - 20:33:26 UTC