@poochner said:
Has anybody here ever worked on a multi-million dollar government contract that went perfectly?
Yes. I have.
@poochner said:
Has anybody here ever worked on a multi-million dollar government contract that went perfectly?
Yes. I have.
@skippy said:
@KattMan said:Personally I prefer the idea of one point of return so I would write the following:
I tend to follow this as well, but as some deep logic can get complicated it can really take away from readability, especially in parsing functions. You end up with a lot of if/else's that cause clutter.
Each method has their appropriate place. I've been in countless arguments with people about this.
If you end up with a lot of it/elses that cause clutter, then you should be using some other construct.
@CapitalT said:
And what if the guy is impotent? or have STD? or is a faggot? etc...
I imagine faggots want to get laid too...
That was awesome! Full marks for originality, at least.
When I worked at the superb Australian carrier Telstra, -48V was the most common supply voltage in the exchanges. Of course, Telstra isn't normal, so I don't know if that counts elsewhere.
Australia got rid of its 1 and 2 cent coins quite some time ago, and I don't miss them at all. Shops can still charge $1.99 for something - if you pay cash it gets rounded to the nearest 5c, but credit or debit cards (or cheques, but who uses those?) users will pay the $1.99.
MSDN is full of examples that should never be used in practice. The majority of the ASP.NET sample code is unbelievably bad!