RE: GCC's statement expression extension

["Akbar A." <syedali011 at earthlink dot net>]

hey guys,
i know things are getting really stressful but (this relates somewhat to
extensions ;-),

i _really_ like to write my code as portable as possible (you never know
what your code ends up running on :-)

currently i am writing most of my software code in C++.
I am not using any stl or heavy usage of stuff i think is "icky" or
things i would feel to be non-trivial for compiler writers (if i have to
read spec more than 4 times, it has to be non-trivial for "compiler writers"

these are
templated types
and stl.
is there anything else i should be watching out for?
or should i go full steam with C++, and hope compilers will churn out
correct executables.
btw, when bjarne is writing his c++ book, does he have an actual compiler
that does _ALL_ of the things he does?
i saw at one of the c++ commite sites, that bjarne posted a message saying
there is a compiler problem generating some fault, which is causing his
manual to be false. if this is so, how could he write a book about a
"feature" (diffren compiler?)


so many thanks.

peace.
akbar A.

"We want technology for the sake of the story, not for its own sake. When
you look back, say 10 years from now, current technology will seem quaint"
Pixars' Edwin Catmull.


-----Original Message-----
From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org]On Behalf Of
Mo McKinlay
Sent: Thursday, July 27, 2000 11:30 PM
To: Marc Espie
Cc: torvalds@transmeta.com; gcc@gcc.gnu.org
Subject: Re: GCC's statement expression extension


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

# Of course, if resources were infinite, you would have lots of developers
# being able to maintain undocumented features of gcc forever.

AFAIK, statement expressions *are* documented, and have been for some
time. (I was reading about them in the texinfo docs the day before this
discussion arose).

- --
Mo McKinlay             Chief Software Architect          inter/open Labs
- -------------------------------------------------------------------------
GnuPG Key: pub  1024D/76A275F9 2000-07-22 Mo McKinlay <mmckinlay@gnu.org>





-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE5gQwpRcGgB3aidfkRAocIAKDfL76HBd+e9u5oLUdwDAB7bUsXTACg5dM3
g5MKgaDxzunEU84PTp/wJ9A=
=1W0d
-----END PGP SIGNATURE-----