> > I think what bilge was trying to point out is that there should be > absolutely no change on existing software with or without the scheduler > running (for software not using fibers). > I thought the same. But where would you hide Fibers? They are part of the language.
The existence of Fibers is an unpleasant issue in the context of language design. Essentially, they break the integrity of the implementation by creating a "backdoor" for user-land. So... various ways can be devised to disguise this fact, but they will all have drawbacks. Of course, you can create the Scheduler before starting the script and run the script inside a Fiber. But I'm sure there will be someone who will say they don't like this approach. Ed.
