* Reply to a message in CARBON_COPY.

Peter Karlsson wrote to Bo Simonsen about ''Soupgate'':

 -=>> Note: Copied from ARTWARE by WIMM 1.31

 >>> Turns out that g++ is not the same as gcc :)
 >> It definately not!

 PK> g++ is just a wrapper for gcc. If you call gcc with the correct
 PK> parameters (generally, a file name recognized as C++ source) it
 PK> will work just like g++ does.

Yes I meant so, I couldn't just remember the correct parameters. :-)

 PK> There's a difference in how g++ calls the linker if you ask it to
 PK> link the program for you (instead of calling the linker manually),
 PK> though. I've been bitten by that more than once. That's why I
 PK> usually stick to calling g++ explicitly instead of using gcc with
 PK> flags.

Is it just me, or do G++ not allow that I am defining a function indirect?
(With out a prototype).

gcc allows me that, it do just give me a warning, not a error like g++.

Bo

--- timEd/Linux 1.11.b1