🚀 go-pugleaf

I recently read a review of the Manx/Aztec C system in an the electronic
magazine recently posted.  It seems to be quite good, but there are a few
points I would like some knowledgeable person to clarify.  Since you can
declare procedures to be "pascal" in some way so the compiler can reverse
the argument list itself and generate an inline call, what does this do
for the string converstion problem.  One of the greatest plusses in the
Megamax system is that the issue of string conversion is handled completely
by the interface library, except for some obscure cases like filterprocs
called from modal dialogs.  Does the Manx/Aztec system also try to do
string conversions, or make me toss them in?  Also, does the "pascal" 
declaration apply to function I define, as opposed to an interface spec
for a library routine? IE, can I write filterprocs without asm glue?
The M/A shell environment sounds just like what I want, IF you can use
desk accessories from the shell.  Sound silly??  I can get in and out of
Mockwrite having fixed a bug by the time Edit rubs the sleep from its eyes,
ramdisk or no.  However, having a pseudo-vi might be worth the wait - years
of electric-C finger macros highly tuned to vi are hard to turn off ONLY
when I am using my Mac. 

Thanks for any information.

	-Mike