Re: pascal equivalent of python "sleep"

On 2008-05-09, thomas.mertes@[EMAIL PROTECTED]
 <thomas.mertes@[EMAIL PROTECTED]
> wrote:
>> Well, I base myself on K & R (appendix C of the 2nd edition to be
exact).
>
> That is a good C reference. For a ****table Pascal the ISO 7185
> Pascal (available here: http://www.standardpascal.org/iso7185.html)
> minus the things that are not available under Borland Pascal/Delphi
> must be used (this is descibed as answer to "Is it possible to write
> in a Pascal subset that will be acceptable to both ISO 7185 Pascal
> and Delphi?" here: http://www.standardpascal.org/pascalfaq.html)

I do not agree that these are the same thing. You are comparing intra
standard compability of C to inter standard compability (giving Borland
that
credit for arguments state) on Pascal.

>> I count 100 calls tops (and that includes some limit constants). Aside
>> from basic file I/O (which is the roughly the same subset in Pascal)
>
> Well not exactly. What about 'remove', 'rename', 'fseek', 'ftell'?

Simply a result of definition at a different time, when the file concept
was
less used. Same with why both don't sup****t GUI, while that is also
considered pretty universal today. Or thread su****t, or, or, or. 

The point is that you can bicker about C having a handful of functions
more
or less, but it is a far, far cry of the number of calls needed to write a
modern app TODAY. And if subset A is 0.1% of the calls, and B 0.2% is
irrelevant.

And I don't have enough time to start a yes/no discussion about every one
of
them, so I skip them.