Xref:	news2.mv.net comp.os.msdos.djgpp:5889
From:	mschulter AT mach1 DOT mpu DOT com (Margo Schulter)
Newsgroups:	comp.os.msdos.djgpp
Subject:	hello, djgpp
Date:	11 Jul 1996 19:08:17 GMT
Organization:	MP Unlimited, Inc.
Lines:	45
Message-ID:	<4s3jf1$7ab@news.mpu.com>
NNTP-Posting-Host:	mach1.mpu.com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

As someone very new to C, djgpp, and to the wonderful world of GNU
utilities as well, I'd like to congratulate the djgpp team not only
for the quality of the compiler port and utilities but for the outstanding
documentation.

The fact that I could start with README.1ST and the FAQ (v. 2.00), ftp the
recommended files, update QEMM from 7.50 to 7.53 with QPAT3.EXE from
Quarterdeck, set up, and compile my first program without any previous C
experience is a tribute to your effort. Further, the compiler messages
generally tell me what I need to quickly debug my novice-level code; people
tell me that helpful compiler messages are unusual <grin>.

Also, anyone concerned about "djgpp as fatware" might take note that
commercial 32-bit compilers might require 80M or more -- 30-35M is very
reasonable for C, Objective C, C++ -- not to speak of "applets" <grin>
such as grep, make, sed, etc. Not only is info a wonderful way to explore
this new world of C, it's one of the most entertaining programs I've ever
used.

As far as the "57K for hello, world" issue, I assumed correctly that a
sophisticated 32-bit compiler using DPMI might require a bit of overhead.
It might be good just to let a beginner know that this is a normal result.
I understand that the next FAQ will do this.

A couple of small glitches. Using pkunzip -d, I got an overwrite query
because both djcrx200.zip and gcc272b.zip unzip identical versions of libgcc.a
to identical paths. Here pkunzip -d -o -n, as recommended in djtut2_1.zip,
avoided the problem.

Also, I was unable to find any documentation on the tests included in 
djtst200.zip, although this could be my oversight. Running either batch
file in \djgpp\tests results in "Bad command or file name." I notice that
mkexe.bat includes a command path ending with posix\bin\stubify -- and
neither DOS nor I can find such a path (nor does it seem to be in the 
manifest for djtst200). Here a small bit of documentation for a rank newcomer
might be helpful.

However, BUILD.BAT worked fine -- EXAMPLE.C is very humorous <grin>.
Most important, I am able to run my own programs -- a case where the real world
application maybe has worked better for me than the demo <grin>.

Congratulations, and I appreciate the efforts to make this newsgroup not only
expert in its resources but beginner-friendly.

- Raw text -