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

Charlie Gordon wrote:

> "Default User" <defaultuserbr@xxxxxxxxx> wrote in message
> news:3njtbgF1tua3U1@xxxxxxxxxxxxxxxxx
> > 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.
>
> Would you mind posting these ?
> Coding Standards so effective would be very helpful around here.


1. They are fairly long.

2. They are not text files.

3. They are most assuredly copyrighted by the company.

4. They are most assuredly considered sensitive information by the
company.


The first two would preclude posting to this newsgroup (besides
possibly being off-topic). The second two would preclude posting them
anywhere.



Brian
.