Re: Why C/C++ errors are SO obscure/devious??
- From: gordonb.uq81k@xxxxxxxxxxx (Gordon Burditt)
- Date: Tue, 30 Aug 2005 22:23:04 -0000
>This can be efficiently handled in the IDE (Integrated development
>Environment).
>
>In the IDE of lcc-win32, when you save a file, the IDE will check for
>1) mismatched braces, parentheses and brackets
>2) Syntax errors
>3) Mismtached #if/#ifdef
Does this mean I can't save the program until I've finished typing
it in? I don't generally like leaving unsaved changes in an editor
more than a couple of minutes. And I may not want to finish up the
statement I'm in the middle of typing in when the phone is ringing
or when my boss is calling me into a meeting. That goes triple
when the UPS starts beeping and I know I don't have much time left
until the computer loses power.
>In the case of mismatched braces it will keep stack of positions
>of opening braces and in most cases it will be able to tell you
>where the opening brace is that it is mismatched.
>
>I do not think that this is the job of the compiler itself but it is
>the job of the environment where you build your programs.
Gordon L. Burditt
.
- References:
- Why C/C++ errors are SO obscure/devious??
- From: Massimo Soricetti
- Re: Why C/C++ errors are SO obscure/devious??
- From: jacob navia
- Why C/C++ errors are SO obscure/devious??
- Prev by Date: Re: while (1) vs. for ( ;; )
- Next by Date: Re: compare a large number of variables
- Previous by thread: Re: Why C/C++ errors are SO obscure/devious??
- Next by thread: Re: Why C/C++ errors are SO obscure/devious??
- Index(es):
Relevant Pages
|
