[comp.sys.ibm.pc.programmer] Microsoft C 6.0 - Documentation format

leadfoot@leftlane.ucs.dec.com (Mark Curtis) (05/01/90)

One quick question.  If someone orders the upgrade from C5.1 to C6.0
will they receive the EXACT same documentation that is in a new C6.0
package?  I'm getting the idea they don't.  Just what EXACTLY
is the difference between the upgrade kit and an off the shelf new
package?

Opps .. Q #2
How much disk space does this on-line doc system eat?  I hope it uses
compression of some kind.

Thanks,
Mark

dubose_b@wums.wustl.edu (Bob DuBose) (05/02/90)

In article <1990Apr27.115023.3401@watserv1.waterloo.edu>,
tom@mims-iris.waterloo.edu (Tom Haapanen) writes:

> Sounds like you have to use their editor for this.  Do they provide specs so
> you can write your own vi macros?  :)  If using the integrated environment is
> the only way to get online help, I'll definitely have to get the book.

Unfortunately, for now the only _seamless_ way to have point-and-shoot
access to the online help is from the editor.  The editor is a rewrite of
the "M" editor supplied w/ C 5.1 and other languages, bound into the PWB. 
There's been a lot of complaints on the docs both for the RTL and PWB.  MS
does show a few examples on how to write extensions to the editor, but it
can take some digging around to find them.  You can replace it with your
own (like brief), but lose the instant quick-help access.  QH is available
from the command line (QH [object]), but to access it from something like
brief you'd have to write your own macro to load it manually.

------------------------------------------------------------
Bob DuBose                           dubose_b@wums.wustl.edu
Department of Genetics                    bdb@agar.wustl.edu
Washington University in St. Louis
------------------------------------------------------------

toma@tekgvs.LABS.TEK.COM (Tom Almy) (05/02/90)

Everybody has been complaining about the poor reference section in the
new version (I'll keep my old version 5 manuals, which BTW I also use when
I am programming using Turbo C!), but I also pity the poor first time
buyer. There is virtually no introductory material either!

I'll stick with the command line invocation of the compiler. PWB is too
clunky. It unloads itself whenever you start a compile. It runs nmake with
every step you take. Borland's Turbo environment works much better.

Users need to pretty much dedicate half a DOS <4.0 partition to it. This
program is a monster.

I couldn't get the sample programs to compile without  several hacks to the
make file.

Its completely incompatible with 386/MAX, and when I switched to their
HIMEM.SYS I crashed because their new HIMEM.SYS is incompatible with my disk
cache.

The compiler, though, generates much better code than my old 5.0 (I never
bothered with 5.1), and I'll stick with Epsilon and NDMAKE for my development
environment. (Hey, I also use SYMDEB!)

Tom Almy
toma@tekgvs.labs.tek.com
Standard Disclaimers Apply

adyer@wyse.wyse.com (Andrew Dyer x2446) (05/03/90)

My solution was to use the 'HELPMAKE' program to unencode the .hlp
files included with the system. After that, I ran the whole mess through
MicroEmacs and separated the wheat from the chaff. I divided up the 
sections into separate named files, put them in a special directory, and
I can then load them into emacs in a separate buffer when I need them.

There are some drawbacks, of course. There is no automatic hyperlink-like
capability, but at least I'm freed from using the quickC editor! :-)
Now, if I just had the cashola to spring for a package with codeview for
debugging....
{uunet, mips, decwrl}!wyse!adyer  adyer@wyse.com
 Now I'm having INSIPID THOUGHTS about the beatiful, round
 wives of HOLLYWOOD MOVIE MOGULS encased in PLEXIGLASS CARS
 and being approached by SMALL BOYS selling FRUIT..

tom@mims-iris.waterloo.edu (Tom Haapanen) (05/03/90)

Andrew Dyer x2446 <adyer@milo.UUCP> writes:
>My solution was to use the 'HELPMAKE' program to unencode the .hlp
>files included with the system. After that, I ran the whole mess through
>MicroEmacs and separated the wheat from the chaff. I divided up the 
>sections into separate named files, [...]

Hey, if I can do this, I'll just run the files through ctags, and when I
need help, I'll just hit ^[ and presto...  :)

[ \tom haapanen --- university of waterloo --- tom@mims-iris.waterloo.edu ]
[ "i don't even know what street canada is on"               -- al capone ]

tomr@ashtate (Tom Rombouts) (05/09/90)

Just as long as Naba Barkakati updates his "bible" series
of books we won't have to worry about the docs or lack thereof!
:-)

Tom Rombouts, Ashton-Tate, tomr@ashtate.A-T.com
Voice: (213) 538-7108