Re: while (1) vs. for ( ;; )

Richard Heathfield wrote:

> Default User said:
>
> > Richard Heathfield wrote:
> >
> >> No. In my experience, people in the world of professional
> programming >> prefer:
> >>
> >> * enormous functions
> >> * multiple exit points from functions and loops
> >> * multiple entry points, if they can get them
> >> * spaghetti logic
> >> * tight coupling
> >> * vry shrt var nms
> >> * evnshrterfnnms
> >> * low cohesion
> >> * lots of debugging
> >> * hardly any testing
> >> * lots of maintenance
> >
> >
> > That's not been my experience.
>
> You've been a very lucky chap. (And, on occasion, so have I.)

Perhaps luck in that the software here has generally been written to
Common Coding Standards (if ERT opposes it, it must be good) which
either forbid or recommend against most of the things on your list.
Naturally, debugging, testing, and maintenance are different, not
really things controlled by a standard.



Brian
.

Relevant Pages

  • Re: [OT] Re: sob..Someone can help me????plsss
    ... Richard Heathfield wrote: ... recommend only using a full stop when the word has been truncated at ... but of course whether it is a *good* standard is a matter of ... opinion. ...
    (comp.lang.c)
  • Re: How to scan C files to find the required include files ?
    ... Richard Heathfield wrote: ... snip ... ... > If you had to do this on a regular basis, I'd also recommend ...
    (comp.unix.programmer)
  • Re: opening a sequence of files
    ... Richard Heathfield schreef: ... >> Here's some hackier code that's more efficient, ... >> recommend using it unless you understand it. ...
    (comp.lang.c)
  • Re: purge like utility in c
    ... Richard Heathfield wrote: ... It is not possible to write a program that will point out all possible leaks in any arbitrary program, with no false positives; to do so would be equivalent to solving the Halting Problem. ... You can recommend valgrind, but when I recommend a garbage ...
    (comp.lang.c)
  • Re: Time to ask?
    ... Richard Heathfield wrote: ... What were you expecting to happen? ... the "debugging" bug. ...
    (comp.lang.c)