Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mimsy!cvl!umd5!brl-adm!adm!PEPRBV@cfaamp.bitnet
From: PEPRBV@cfaamp.bitnet
Newsgroups: comp.lang.c
Subject: #pragma
Message-ID: <7365@brl-adm.ARPA>
Date: Thu, 14-May-87 00:45:00 EDT
Article-I.D.: brl-adm.7365
Posted: Thu May 14 00:45:00 1987
Date-Received: Sat, 16-May-87 08:10:34 EDT
Sender: news@brl-adm.ARPA
Lines: 15

I recognize  that #pragma  is non-portable,  but most  of the C I
write only sees one compiler  and one machine.   It is awkward to
set  up  a makefile  which  uses  different  compiler  flags  for
different  routines  so I would  like  to be able  to put some of
these flags in the source code by using #pragma.   Examples would
be switches  to optimize  for speed or code size, warnings to the
compiler  that different  pointers  point to the same object,  so
certain optimizations  shouldn't  be done, turn on stack overflow
checking for stack-greedy functions, or force use of a particular
memory model.  All but the last of these would seem to make sense
in any environment,  even if the details of what the commands  to
the compiler  are implementation  dependent.   So, I guess I vote
both  for  compiler  writers  to implement  #pragma  commands  to
control things which could also be command line options,  and for
ANSI to set some general standards for syntax.