Re: Compiling VB6 programs
- From: "Michael D. Ober" <obermd.@.alum.mit.edu.nospam>
- Date: Thu, 14 Jul 2005 01:23:12 GMT
Most languages, including VB.Net, continue syntax checking even after the
first error. That way you can fix a bunch of errors at the same time. By
the way, the background compiler in VB 2005 (.Net 2.0) will display the
first 100 compilation errors as you edit, allowing you to go fix them
without waiting for a compile. The only reason that VB 6 doesn't continue
with the compile was simply laziness on the part of the VB 6 compiler
writers. It's easier to stop the compile on the first error.
Mike Ober.
"Rick Rothstein" <rickNOSPAMnews@xxxxxxxxxxxxxxxxx> wrote in message
news:O1qrEo8hFHA.3064@xxxxxxxxxxxxxxxxxxxxxxx
> > > > I've not tested, but what does the command line /make option do on
> > > > error?
> > >
> > > It stops on the first error and shows a messagebox before quitting.
> >
> > That sucks... :)
>
> Wouldn't it always have to stop of the first error it comes across?
> Unless you are expecting it to be nothing more than a syntax checker
> (which I guess Microsoft could have provided as an option), it tries to
> compile the code and finds something it doesn't know how to compile
> around... what would you expect it to do from here? It pretty much
> doesn't know how to continue past the error it found, how could it skip
> over that and look for another error?
>
> Rick
>
>
.
- References:
- Compiling VB6 programs
- From: Oman
- Re: Compiling VB6 programs
- From: Ken Halter
- Re: Compiling VB6 programs
- From: Duane Bozarth
- Re: Compiling VB6 programs
- From: Ken Halter
- Re: Compiling VB6 programs
- From: Duane Bozarth
- Re: Compiling VB6 programs
- From: Rick Rothstein
- Compiling VB6 programs
- Prev by Date: Re: Check if file is in use
- Next by Date: Re: Compiling VB6 programs
- Previous by thread: Re: Compiling VB6 programs
- Next by thread: Re: Compiling VB6 programs
- Index(es):
Relevant Pages
|