If there is a possibility of getting damages out of bad patents lawyers would be swarming around possible victims. All on no-cure no-pay basis. Just like there are in case you hurt your left toe when you slip in a super market.
I agree. Especially for research Matlab is a very powerful tool (in particular with the special purpose toolboxes, Simulink is great!). You will have to think in matrix and vetors to get the speed. I am regularly called by colleagues to fix speed problems with Mathlab applications. Usually it is a for loop that could be vectorised (mostly by the use of boolean array's).
Why is Matlab so fast? Well, it's nothing more as an easy frontend for the Fortran libraries. That's where the speed is: FORTRAN.
The practitioner of literate programming [literateprogramming.com] can be regarded as an essayist, whose main concern is with exposition and excellence of style.
Yes, it is very nice, but try to find good programmers who are good essayists too. I am afraid there aren't many master Knuths around.
It will (probably) get smaller, a reduction is more likely the bigger the file is. If you really think this is true why don't you cash The $5000 Compression Challenge and of course the Slashdot article.
Well, all this compression BS was discussed over a thousand times but most people keep on dreaming.
But de important part isn't the indentation style. The important is that it describes the prefered constructions to solve certaint types of problems. It describes the rules for a good, uniform implementation.
And DO NOT make it a book of rules. For every rule there has to be argumentation why it has to be this way, including examples and they main advantages of the rule (improves robustness, maintainability, clarity, portability, uniformity).
The coding standard will help new and unexperienced to build good solid code. The professionals will like it because after reading the coding standard they know what is kind of code is expected from them.
And, maybe most important, will keep the hackers under control. Hackers won't adhere to rules just because they are the rules. But if they know why the rules are as they are they will use them.
I was a hacker who was coding only his way too, I didn't like rules because they made no sense to me. Right until I read Patrick Savalle's (Synalyse (sorry guys, dutch only)) C coding standard, that one made sense.
I am still using it, both for private and professional work (on most jobs there isn't a coding standard, the one I bring is very welcome and if there is an coding standard it is mostley only about identation so those are replaced just as easy).
No opinion
Case insensitive- doesn't make a huge difference, but I do see it causing confusion as the _ ignoring will.
This depends on what you are doing. I do a lot of physics related coding. One way to create clear and readable programs is to stay as close to the mathematical notation as possible. And in physics (and mathemathics) the case is essential:
V = Volume
v = speed
Phi = flow
phi = angle
etc.
Being caseinsensitive will ban this practice.
Of course, those who are used to case insensitivityhad never a problem with it. Those who are used to it will miss it. Maybe we know that John_Smith and JohnSmith are the same person. But we all know that Annemarie and Anne-Marie are different girls.
There is no overwhelming need to be case insensitive. It is a choise.
Most (non ICT) people I know are very case sensitive with their e-mail adress. They are treating it as being case sensitive though we all know it isn't. When this comes quite natural why don't make use off it in a programming language?
I'd be more worried about the beam suddenly stopping, and focusing on one spot on the retina for too long.
Trust me, you will find it quite hard to look at a beam with an intensity big enough to damage your eye. Your eyes will shut by reflex. Sure when you manage to look into such a beam you will see some after images for a few minutes but that will be all.
Further there are no invisible wavelengths damaging your retina without you knowing it. Like in sunlight.
Trus a company that said "We will make an great OS for I386, Sparc, Power PC and Alpha.". Now, some years later look at the result: all support for Sparc and Power PC has been dropped long ago. The Alpha processor was the last one to loose support. Would you trust your critical systems and applications on such a company? Would you belive such a company to support new 64-bit processors? What if they drop support for your platform? You are left in the cold. There in _NO_ source code available so you can't do your own maintenance. Clearly no one going for long time stability would even think about using software of a company with such a history... Ech Ni!
Slashdot Mirror
If there is a possibility of getting damages out of bad patents lawyers would be swarming around possible victims. All on no-cure no-pay basis. Just like there are in case you hurt your left toe when you slip in a super market.
Hans
I agree. Especially for research Matlab is a very powerful tool (in particular with the special purpose toolboxes, Simulink is great!). You will have to think in matrix and vetors to get the speed. I am regularly called by colleagues to fix speed problems with Mathlab applications. Usually it is a for loop that could be vectorised (mostly by the use of boolean array's).
Why is Matlab so fast? Well, it's nothing more as an easy frontend for the Fortran libraries. That's where the speed is: FORTRAN.
Cu, Hans
The practitioner of literate programming [literateprogramming.com] can be regarded as an essayist, whose main concern is with exposition and excellence of style.
Yes, it is very nice, but try to find good programmers who are good essayists too. I am afraid there aren't many master Knuths around.
It will (probably) get smaller, a reduction is more likely the bigger the file is.
If you really think this is true why don't you cash The $5000 Compression Challenge and of course the Slashdot article.
Well, all this compression BS was discussed over a thousand times but most people keep on dreaming.
Hans
But de important part isn't the indentation style. The important is that it describes the prefered constructions to solve certaint types of problems. It describes the rules for a good, uniform implementation.
And DO NOT make it a book of rules. For every rule there has to be argumentation why it has to be this way, including examples and they main advantages of the rule (improves robustness, maintainability, clarity, portability, uniformity).
The coding standard will help new and unexperienced to build good solid code. The professionals will like it because after reading the coding standard they know what is kind of code is expected from them.
And, maybe most important, will keep the hackers under control. Hackers won't adhere to rules just because they are the rules. But if they know why the rules are as they are they will use them.
I was a hacker who was coding only his way too, I didn't like rules because they made no sense to me. Right until I read Patrick Savalle's (Synalyse (sorry guys, dutch only)) C coding standard, that one made sense.
I am still using it, both for private and professional work (on most jobs there isn't a coding standard, the one I bring is very welcome and if there is an coding standard it is mostley only about identation so those are replaced just as easy).
Just my EUR 0.02, Hans
This depends on what you are doing. I do a lot of physics related coding. One way to create clear and readable programs is to stay as close to the mathematical notation as possible. And in physics (and mathemathics) the case is essential:
V = Volume
v = speed
Phi = flow
phi = angle
etc.
Being caseinsensitive will ban this practice.
Of course, those who are used to case insensitivityhad never a problem with it. Those who are used to it will miss it. Maybe we know that John_Smith and JohnSmith are the same person. But we all know that Annemarie and Anne-Marie are different girls.
There is no overwhelming need to be case insensitive. It is a choise.
Most (non ICT) people I know are very case sensitive with their e-mail adress. They are treating it as being case sensitive though we all know it isn't. When this comes quite natural why don't make use off it in a programming language?
Hans
Trust me, you will find it quite hard to look at a beam with an intensity big enough to damage your eye. Your eyes will shut by reflex. Sure when you manage to look into such a beam you will see some after images for a few minutes but that will be all.
Further there are no invisible wavelengths damaging your retina without you knowing it. Like in sunlight.
Trus a company that said "We will make an great OS for I386,
Sparc, Power PC and Alpha.".
Now, some years later look at the result: all support for Sparc and Power PC has been dropped long ago. The Alpha processor was the last one to loose support.
Would you trust your critical systems and applications on such a company?
Would you belive such a company to support new 64-bit processors?
What if they drop support for your platform? You are left in the cold. There in _NO_ source code available so you can't do your own maintenance.
Clearly no one going for long time stability would even think about using software of a company with such a history...
Ech Ni!