[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Language-oriented vs primitive-oriented



My interpretation of the lack of proper language support for 754 (1985)
is inertia, and the general unease of some languages to deal with
exception handling -- perhaps because older languages like PL/I went
overboard and left a bad taste...

I fully agree that the new standard should strive to prevent this from
happening again, and should therefor give explicit guidance and even
mandatory requirements to the providers of programming environments.

The problem is the tension between the language-oriented view and the
hardware-oriented view that may still be in the backs of participant's
minds.   This kind of tension is probably inevitable in committee work,
something to which I am a newcomer, so I have no good ideas yet on how
to deal with this.  Occasionally I do get the impression that we are
trying to push mutually incompatible options, or worse, option groups,
and the (sometimes) fickleness of voting may approve one of group A and
another of group B, leading to more trouble than before.

Michel.
Sent: 2006-08-04 15:26:15 UTC

754 | revision | FAQ | references | list archive