MacApp->C++->A/UX

[Kent Sandvik]

In article <3151 at skivs.UUCP> jmm at ski.UUCP (Joel M. Miller) writes:
>MacApp, so far as I know, contains Object Pascal and requires Pascal
>libraries, and so does not produce code that could be compiled by
>cc under A/UX.

Sorry, a slight misconception, A/UX cc produces COFF files. MPW Pascal,
C, Asm and C++/C produces MPW object format files. Object classes that use
a special PascalObject C++ base class for their class hierarchies can
be linked with both Object Pascal and C++ code modules with the
MPW linker.

>I suppose that the reason for providing MacApp for MacOS -- to make it
>easier to write Mac-like applications than not -- applies to A/UX as well,
>and so expect that Apple has provided, or soon will provide, a version
>of MacApp using C++ instead of Object Pascal, along with the required A/UX
>libraries.  So:

The new MacApp 3.0 makes use of PascalObjects as the base class, in
order to create method tables (instead of the normal vtables) so 
people could use these classes/libraries from both Object Pascal and
C++ with the MPW linker. It has really nothing to do with A/UX - more
of a switch to C++ in order to build better class internals which are
not visible from the C++ or Pascal code.

>	++  If MacApp++ exists, how do I get it (beta`s welcomed)?

Just now a selected list of developers have access to the first alpha
version of MacApp 3.0. A later alpha release will be available from the
so called ETO CDs.

>	++  If it is comming, when?

Real soon now!

>	++  If not, why not???

Hmm, a better question would be "Are there any plans to support COFF
format from the MPW environment?", or "Will the A/UX linker support
linking of MPW object format files?", or "Will there be a MPW Shell
that runs on top of A/UX?, and similar questions :-).


Regards,
Kent Sandvik

-- 
Disclaimer: Private and personal activities on USENET, non-company sponsored