#Aztec C bye-bye …
9 messages in this thread
A sysop (Jeff Davis) on the Manx BBS (+1 908 780 6363) stated in a message
January 19 that the Aztec C product is frozen, and no further updates are
planned. *Sigh*. Time to buy SAS, I guess. With no competition, what will
happen to the Amiga compiler market?
—–> Brian Simmons, Denver, Colorado. – via Whap!
>Aztec C product is frozen, and no further updates are planned.
I can confirm what Brian is saying as I saw the same message.
That applies to their AmigaDOS version only though as I understand it.
>With no competetion, what will happen to the Amiga compiler market?
I wouldn't discard DICE C too quickly, or maybe others.
Especially since DICE is going commercial. Even if not though,
I don't see any problem with the Amiga compiler market.
SAS is going strong, as they justly earned it. And of course
there is Comeau C++, which uses SAS (and Aztec (and Dice support is now in
beta)). And of course there are other languages.
Bottom line to me: the Amiga compiler market is getting better not worse.
Don't assume that competition has been driving SAS Institute's
efforts. We had the edge on Aztec with our 5.10 compiler.
The real story is that we have people interested in doing it,
and the support of upper management (as long as we are
profitable). Manx was certainly a force to be reckoned with
for Lattice C 4.0 and 5.0 (ask John Toebes, who pulled us
even with them at that time) but they really didn't figure in
to 6.0 planning or development as a factor.
–Doug
Brian:
Does SAS C have any better support for overlays than Aztec C?
Regards, Tom
I must report with considerable dismay that at least one reported bug
is NOT fixed in SAS C 6.2. It WAS reported via EMITS (which now claims no
current record of it). Of course, I didn't get the update until late
Friday night (after all you guys had gone home) and started testing
immediately (looks like you've fixed another bug we reported AFTER this
one). When I sent internet mail reporting that it wasn't fixed, I was
told that it wasn't in the current database. In case you can retrieve
things from some archive, the number originally assigned was 1500811.
If you canNOT find the bug report, here is the entire sample program.
void main(int argc, char **argv)
{
char funnystring[] = "0123456789abcdefghijklmnopqrstuvwxyz";
register char *text = &funnystring[3];
register int count;
register char cur;
for (count = 36-3; count > 0; count–)
{
cur = text [1]; *text++ = cur;
}
puts(funnystring);
}
try sc optimize link <whateveryoucallthisfile>
then run the resulting program.
DICE is still being worked on. A friend of mine has been using it for a
project, and really likes it. I'm thinking of picking it up myself.
There's a version of it in the library, and when you register the product
you'll be able to get updates.
Steve
I haven't seen the commercial DICE. Does it offer anything that SAS
doesn't?
…Steve
I don't think the commercial DICE is out yet, but as I said, it's being
worked on. The only version I'm aware of is the shareware one in the
library. As for features, I don't know. I already own Lattice, but I
figure that for the relatively cheap registration of DICE it's worth a
look. As soon as I get some time I'll be looking into it a bit more.
Steve
I wouldn't worry all that much – the SAS compiler is a terriffic product.
–Ben
…via AutoPilot