🚀 go-pugleaf

osmoviita@cc.helsinki.fi writes:

>Q1: When you say it is DPMI, VCPI, and 'vanilla' DOS compliant, does this 
>mean that the programs compiled with it are also? And can you compile 
>a program which is DPMI and VCPI compliant at the same time or do you need 
>to compile different versions for each case?

There is a version of the compiler that is compliant, and you can create 
applications that are compliant (the -mx memory model).  The same 
application will run under all three environments completely transparent to
the C/C++ programmer (the assembly language programmer can get in trouble 
when attempting to access real mode DOS and BIOS services).

>Q2: What kind of improvements there is in the integrated developing
>environment? I have only read some test saying Zortech is nice but Borlands
>environment is better -- not seen Zortech compiler yet. Ie. is it also for
>beginners?
>(There is some people who stick with QuickBasic until there is
>an easy integrated 32 bit C with good graphics support and documentation
>because eg. Borland C++ is not an answer for them).

I've never used anyone's 'environment'.  I use a text editor, MASM, MAKE, 
and the Zortech librarian and linker.  I use the Zortech compiler when
running parts of the test suite.

Call Zortech or send email to support@zortech.com for information on ZWB.
I've never used it.

>Q3: Is it possible to write inline assembler code like in Borland and
>Microsof products? If not what to use with it if there is a need for some
>lines of assembler code? (Perhaps the novice has got an assembler listing 
>what does exactly what (s)he wants and (s)he is afraid of even thinking 
>to use separate XYZ assemler package which nobody has heard about.)
>I am interested of the 386 extender version.

I use MASM.  Pharlap's 386ASM also works with it.  There is some support for
inline assembler but I don't think it's as extensive as some other vendors.
I don't use the compiler much (just for testing) contact support@zortech.com
for more details.

[... questions I can't answer deleted...]

>Q8: How tested, buggy, stable,...

Quantitatively I don't know how to answer this...

Various portions of this release been in alpha and beta for several months.
We have a test suites that has been extensively expanded for this release.
Each of the developers (for the environment, the compiler, the graphics,
the DOS extender, etc, etc) is responsible for creating and maintaining their 
own test suite and doing regression testing.  Tech support runs the examples
from the manuals through.  The stated intention at the developers meetings
was to stress quality over new features in this release.  I know that many
features were cut so that the time could be spent on bug reports.  
-- 
uunet!proto!doug
doug@proto.com