Related articles |
---|
[27 earlier articles] |
Re: Why do we still assemble? rfg@netcom.com (1994-04-13) |
Re: Why do we still assemble? rfg@netcom.com (1994-04-13) |
Re: Why do we still assemble? zstern@adobe.com (1994-04-13) |
Re: Why do we still assemble? mps@dent.uchicago.edu (1994-04-14) |
Re: Why do we still assemble? bill@amber.ssd.csd.harris.com (1994-04-14) |
Re: Why do we still assemble? hbaker@netcom.com (1994-04-14) |
Re: Why do we still assemble? djohnson@arnold.ucsd.edu (1994-04-15) |
Re: Why do we still assemble? philw@tempel.research.att.com (1994-04-15) |
Re: Why do we still assemble? pardo@cs.washington.edu (1994-04-15) |
Re: Why do we still assemble? wirzeniu@cc.helsinki.fi (Lars Wirzenius) (1994-04-16) |
Re: Why do we still assemble? hbaker@netcom.com (1994-04-16) |
Re: Why do we still assemble? hrubin@b.stat.purdue.edu (1994-04-17) |
Re: Why do we still assemble? bevan@cs.man.ac.uk (Stephen J Bevan) (1994-04-18) |
Newsgroups: | comp.compilers |
From: | djohnson@arnold.ucsd.edu (Darin Johnson) |
Keywords: | C++, design |
Organization: | Compilers Central |
References: | 94-04-032 94-04-090 |
Date: | Fri, 15 Apr 1994 01:57:56 GMT |
> It is perhaps worthy of note that implementors do not have this option
> in the case of C++. So-called `asm directives' are a part of the current
> draft C++ standard. Implementors *must* provide them.
Yes, but what does the (draft) standard say about the semantics? Could we
perhaps have an asm in C++ for the Cray that accepts VAX assembler?
(causing exceptions at run time :-)
Such things are inherently unportable, even between different compilers on
the same machine. Thus it makes more sense to have a general directive
for non portable things (ie, ANSI C's pragma), rather than trying to
create different directives for different nonportable constructs.
--
Darin Johnson
djohnson@ucsd.edu
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.