Re: while (1) vs. for ( ;; )
- From: Richard Heathfield <invalid@xxxxxxxxxxxxxxx>
- Date: Tue, 30 Aug 2005 08:17:10 +0000 (UTC)
Christopher Benson-Manica said:
> Richard Heathfield <invalid@xxxxxxxxxxxxxxx> wrote:
>
>> I'm quite unlikely to use multiple returns
>
> Would you suppose that such a view is common in the world of
> professional programming?
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
> My work experience is still quite limited,
> and it's hard to tell ubiquitous programming conventions from
> idiosyncratic oddities...
Right. I think the above list is pretty much universal. I've only worked on,
perhaps, three client sites where it wasn't observed.
--
Richard Heathfield
"Usenet is a strange place" - dmr 29 July 1999
http://www.cpax.org.uk
Email rjh at the above domain
.
- Follow-Ups:
- Re: while (1) vs. for ( ;; )
- From: Default User
- Re: while (1) vs. for ( ;; )
- References:
- while (1) vs. for ( ;; )
- From: Michael B Allen
- Re: while (1) vs. for ( ;; )
- From: Richard Heathfield
- Re: while (1) vs. for ( ;; )
- From: Alan Balmer
- Re: while (1) vs. for ( ;; )
- From: Richard Heathfield
- Re: while (1) vs. for ( ;; )
- From: Christopher Benson-Manica
- while (1) vs. for ( ;; )
- Prev by Date: Re: while (1) vs. for ( ;; )
- Next by Date: How to free dynamically allocated array?
- Previous by thread: Re: while (1) vs. for ( ;; )
- Next by thread: Re: while (1) vs. for ( ;; )
- Index(es):
Relevant Pages
|