Hi !

 * Reply to msg in SYSOP

On Jan 24 22:20 96, Peter Fitzsimmons of 1:259/414 wrote:

 JP>> Complete ? It is still 60-days limited.

 PF> It's still complete,  even if it times out.  Everything on 
 PF> devcon,except for the Programmer's Toolkit,  has a short 
 PF> license (even though most of them don't time out).

Yes, but the CSDs will not install on the time-limited version of VAC++,
making it worthless for me ...

 JP>> But it is VERY buggy. The Workframe 3 is so slow (even

 PF> I think you mean VisualBuilder.

No, I was really talking about Workframe 3. The makemake is extremely slow.
Plus you can't do much of anything while it is running - thanks to the
single input queue problem. And it is buggy, too. For example,
if you have a DEF file with "def" in lowercase, it will not
recognize it ... ! It took me quite a bit of time to figure that out.
The compiler code seems to be buggy too (my code runs fine with C Set ++
2.1 and Watcom, but not VAC).
And the linker doesn't link my object files.
I tried the VisualBuilder and it didn't seem slow at all, contrary to what
I had heard. It took maybe 15 seconds to start and then operation was quite
smooth. But I am running this on a P100 with 32MB of RAM, accelerated video
(Diamond Stealth Video PCI with 4MB at 1280x1024x65K), NCR Fast SCSI-2 PCI,
and a 6MB/s SCSI-2 hard disk, so it certainly helps.

 PF> You don't have to use it -- people were complaining that 
 PF> they couldn't afford to get devcon and a C compiler (A 
 PF> C[++] compiler does not inherently mean WorkFrame, Visual 
 PF> BUilder GUI Class Libraries, etc). Now devcon has two (IBM 
 PF> and Metaware) to try.

That's true. Given the choice between Metaware and VAC++, I would hesitate.
Metaware is much slower to compile than VAC++ and has a proprietary
preprocessor syntax which require you to rewrite almost all definitions.
But the code produced is ok, and the linker works.
The debugger in Metaware is still useless, while the one in VAC is very nice.

Julien

--- Msgedsq/2 2.2e