🚀 go-pugleaf

>   > I can't continue with my
>   > work with the lack of functionality I need from CW7.2 on MacOSX...
>
> I cannot imagine there is anything that you cannot do with CWPRO7.2. I
> have even used an older version (CW11) to do the work you are describing
> and I even used MPW for it.

I'm not saying that it's impossible for CW7.2 to do the work I want, it's
just that with it running on MacOSX, and building MacOSX binaries, it's not
as straightforward as it's supposed be.  I even had to rebuild their MacOSX
libraries cause it wasn't even exporting the right symbols.  If I wanted to
manually "configure and set everything up", I'd just go with the tried and
true method of UNIX development, ie a bunch of make files and cc).  Then
why'd I buy CW??

Also, what kind of IDE crashes and locks up whenever it tries to build
(remedied by always doing a full clean between complete builds) let alone I
can't even use the debugger to debug a JNILIB???

CW7.2 works absolutely fine and wonderful on MacOS9; I can't imagine using
anything else.  But on MacOSX, it's a different story...

> Reasons to upgrade might be evolving of the languages (e.g. CW11 does
> not understand templates in C++), easier use or more up-to-date
> installation of related information (header files, libraries or even
> targets). Most of these reasons come into existence when you are working
> on projects that include several programmers on different platforms (or
> only different tools)