Re: Why C/C++ errors are SO obscure/devious??
- From: Massimo Soricetti <massimo_main@xxxxxxxxxxx>
- Date: Wed, 31 Aug 2005 03:39:38 GMT
Joseph S. ha scritto:
I dont know the technical reasons for it, but, the Eclipse Integrated Development Environment (www.eclipse.org) for Java does things a little like this -suggesting at coding time what could be wrong with your code, giving alternatives on a popup textbox to change the type of your variable,. to add a cast here, to remove a line there etc.- It is not complete/foolproof, neither does it claim to be, but for most beginner to intremediate level Java coders it is useful, (of course, it is for the java language) It immediately suggests what could be wrong with your code -So, looking at this proficiency of Eclipse in Java, one wonders whether some of that kind of "interactive" coding can be brought to C.
So, something in this field CAN actually be done... Even if some of my ideas had proven naive, I think that a C "pre-preprocessor" looking for errors and making some guess based on coding style (detected from sources: every programmer has his own coding style, the prepreprocessor should be able to examinate code and detect kind of indentation, of parentheses placement etc) and common error sources and tries to suggest possible causes could eventually be useful...
.
- Follow-Ups:
- Re: Why C/C++ errors are SO obscure/devious??
- From: Eric Sosman
- Re: Why C/C++ errors are SO obscure/devious??
- References:
- Why C/C++ errors are SO obscure/devious??
- From: Massimo Soricetti
- Re: Why C/C++ errors are SO obscure/devious??
- From: Joseph S.
- Why C/C++ errors are SO obscure/devious??
- Prev by Date: Re: Why C/C++ errors are SO obscure/devious??
- Next by Date: Re: confused abt file operations
- 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
|
|