Xref: utzoo alt.religion.computers:2533 comp.windows.ms.programmer:3219
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!slxsys!ibmpcug!mantis!mathew
From: mathew@mantis.co.uk (Giving C News a *HUG*)
Newsgroups: alt.religion.computers,comp.windows.ms.programmer
Subject: Re: ap, Windows BASIC
Message-ID: <2mRu43w164w@mantis.co.uk>
Date: 20 Jun 91 18:24:12 GMT
References: <1991Jun20.034708.2816@maverick.ksu.ksu.edu>
Organization: Mantis Consultants, Cambridge. UK.
Lines: 39

rogerhef@matt.ksu.ksu.edu (Roger Heflin) writes:
> In <4k4q47w164w@mantis.co.uk> mathew@mantis.co.uk (Giving C News a *HUG*) wri
> >>                                                One of the great things
> >> I like about the QB environment is when you press the F2 key, a window
> >> pops up with a list of all your procedures/functions.  Click on the one
> >> you want to look at and bingo.  Very nice.
> 
> >My editor does that, for C, C++, Pascal, Modula-2, Clipper, or any other
> >language you care to tell it about.
> 
> Yes your editor can do that with C,C++,Pascal, .... but you had to take
> time to set it up to work correctly,

No I didn't.  I just put the installation disk in, typed SETUP, and answered
a few questions.  Then I loaded my C program, typed CTRL-G, and it gave me a
list of all the procedures and functions I could jump to.  I then loaded a
Clipper program and did the same thing, and that worked as well.

> Does your editor also do full debugging?

No, my debugger does full debugging.

>                                   QB's debugger surpasses any debugger
> I have found on any Unix machine on relibility and usability.

So?  I thought we were talking about DOS and Windows programming.  I wouldn't
hold up UNIX as a good example of anything much.

> I have never had a QB program 'coredump'.  It is a considerably safer programming
> enviroment compared to C or C++.  

That's mainly because it doesn't have pointers, which is a pretty big price
to pay.  I'd rather be allowed to use pointers, and have the machine bring up
the appropriate line of source code whenever a pointer error occurs.


mathew