2. The Labour Party has a party line that is decided as a group, and all members must adhere to that party line once it's decided.
How can you present yourself as an authority when you don't even know how to spell the name of the Labor party?
Oh, and what of the factions in that party which regularly oppose the 'party line'?
Hey, weren't you saying that to the parent poster? Hmmm, hoist on your own petard, methinks...
Howard is hopeless, but so is Latham. We are in the unfortunate position of having no choice. The minor parties assign preferences to the two major parties, meaning a vote for a minor party is effectively a vote for the major party of their choice, not yours.
As a contract programmer I have worked with a number of companies over the past decade on platforms such as MVS, UNIX, Windows, OS/2 and various embedded systems. Every one of those companies has had a rule that no line is to exceed 80 columns wide.
However... when you actually look at the existing code in every one of those companies they are replete with lines that break the 80 column rule - and new code is no better.
A similar issue arises with tabs vs spaces. I have worked for companies that require only tabs be used [with various tab widths], and companies that require tabs never be used, but when you check existing code it is *always* a mixture of tabs and spaces that sends the formatting to hell no matter how you view it.
I guess those who think they are in charge set rules that satisfy their personal opinions, but the developers [particularly short term contractors] do whatevery they prefer anyway. It is a fact that in most cases the test of a job well done is the reliability and specification compliance of the finished code, not the formatting of the source. So much so, that the company I am with at present is the first to review my source since the early 90s.
The multiparameter APIs in Windows, OS/2 etc don't help, and the casting that is forced upon us by these operating systems is as much to blame as programmers who refuse to adapt.
My personal view is that setting an 80 column rule is a good idea in principle, but as systems become more complex it becomes harder to comply in a meaningful way (ie so the code is more readable, which is the point after all).
For a number of years many RF power transistors have actually been made as a few transistors on the one die with low value resistors in series with each emitter, the lot connected in parallel. They are known as 'emitter ballasted'. If you pop the top off one of the ceramic packs you can actually see the construction with the fine wires connecting to each ballast resistor.
Slashdot Mirror
Napster, Kazaa et al prove you to be right...
So make the WiFI power down when not in use. As far as the standard changes in 802.11, they are backward compatible. Where's the problem?
How can you present yourself as an authority when you don't even know how to spell the name of the Labor party?
Oh, and what of the factions in that party which regularly oppose the 'party line'?
Hey, weren't you saying that to the parent poster? Hmmm, hoist on your own petard, methinks...
Howard is hopeless, but so is Latham. We are in the unfortunate position of having no choice. The minor parties assign preferences to the two major parties, meaning a vote for a minor party is effectively a vote for the major party of their choice, not yours.
As a contract programmer I have worked with a number of companies over the past decade on platforms such as MVS, UNIX, Windows, OS/2 and various embedded systems. Every one of those companies has had a rule that no line is to exceed 80 columns wide.
However... when you actually look at the existing code in every one of those companies they are replete with lines that break the 80 column rule - and new code is no better.
A similar issue arises with tabs vs spaces. I have worked for companies that require only tabs be used [with various tab widths], and companies that require tabs never be used, but when you check existing code it is *always* a mixture of tabs and spaces that sends the formatting to hell no matter how you view it.
I guess those who think they are in charge set rules that satisfy their personal opinions, but the developers [particularly short term contractors] do whatevery they prefer anyway. It is a fact that in most cases the test of a job well done is the reliability and specification compliance of the finished code, not the formatting of the source. So much so, that the company I am with at present is the first to review my source since the early 90s.
The multiparameter APIs in Windows, OS/2 etc don't help, and the casting that is forced upon us by these operating systems is as much to blame as programmers who refuse to adapt.
My personal view is that setting an 80 column rule is a good idea in principle, but as systems become more complex it becomes harder to comply in a meaningful way (ie so the code is more readable, which is the point after all).
For a number of years many RF power transistors have actually been made as a few transistors on the one die with low value resistors in series with each emitter, the lot connected in parallel. They are known as 'emitter ballasted'. If you pop the top off one of the ceramic packs you can actually see the construction with the fine wires connecting to each ballast resistor.