🚀 go-pugleaf

Hi,

I know the macho tools are not for production, but if you put them on a
CD-ROM I expect them to work.

In the stationery readme, it says the there are no known issues, EXCEPT
that Carbon cannot be linked into the project. So how do you expect us to
get the stationery working if we can't even link in the carbon framework?

I tried the C++ Mac mach-o stationery and I'm getting link errors for
symbols that ought to be in carbon.

Another issue is the compilers and linkers seem to be buggy.

in some of my classes I have methods like these in the headers:

virtual var_type functionname() {}
virtual var_type functionname2() {return var;}

These always cause "multiple definition of functionname" errors when you try
to link.
It only happens when they the methods are "virtual". I can work around
this by moving the definition into the .cpp file.  Non-virtual inlines
don't cause this error message.

This source compiles fine as a CFM Carbon app in Metrowerks.

I am also getting a number of multiple definition errors for
_dt_classnames (destructors??). In some cases it is because I have
virtual ~classname() {}

but in other cases the classes don't even have a destructor so I dont
know how to work around it.

I am eagerly awaiting the early release tools and I hope I can download them
off the net because I'm in a hurry! I hope the above problems were fixed
or you have more documentation telling me what I'm doing wrong :)

Adam

askwersky@worldnet.att.net