|
You missed my point. No matter how bugless your program is there is no point if only a supercomputer is needed to run it. Like if we had pc:s like 200mhz pentiums and you shoud run the Longhorn in it. What is the point in it?
|
|
|
|
|
I don't understand what you are trying to say.
Mordok wrote:
Like if we had pc:s like 200mhz pentiums and you shoud run the Longhorn in it. What is the point in it?
Ummm.... I don't think a 500Mhz P2 could run Longhorn, let alone a 200Mhz Pentium.
Aaron Eldreth
TheCollective4.com
My Articles
While much is too strange to be believed,
Nothing is too strange to have happened.
- T. Hardy
|
|
|
|
|
It appears so. It was a symbolic language. The better code is the one that is simpler, less resource using if you compare two codes.
For example if you have a code that has few bugs but a memory usage of few megs and cpu usage only few percents. The other uses cpu 100% because dum desing and complexity but has no bugs. Whichone is better? You can use both but the other works better due to its simplicity, youknow the bugs always can be fixed and there is no such thin as bugless code if you do huge programs.
Another example. Let's assume that there is no bug's in Longhorn, but there are bugs in XP.
Like in this situation you sayed your self:
"Ummm.... I don't think a 500Mhz P2 could run Longhorn, let alone a 200Mhz Pentium."
XP uses less resources hence you can use these same resouces in somewhere else. Now if I use Longhorn and it takes all my resources to have it work what use it is for me? I can't do anything, although there in no bugs. But in XP I can.
I didn't assume that Longhorn would work in 200Mhz cpu.I don't assume it will work decently with my athlon either.
Do you see my point? First do it as simle and as efficient as you can. That it self remowes the bugs that comes from useless complexity. Then you have not as much bugs to fix.
Bugs are often revealed in testing, but you can't test it forever because your code doesn't then benefit anyone and you couldn't because you die in old age before it. Bugless program is a nice ideal but in large programs it's hard if not completely impossible to achieve. Then you'll come back to that resource efficient is a better thing.
ps. I HATE to write this long writings.
|
|
|
|
|
There is nearly no poll without at least one "CListCtrl"-vote.
Would you please be so nice to a clueless CP-newbie an tell me what's up with that CListCtrl... is it the visual implementation of 42, the answer to everything?
|
|
|
|
|
People often type search terms into the wrong boxes, including the one for text answers to a poll. Other people started noticing that, and somehow "CListCtrl" became representative of the mistake - maybe people were searching for it more than other terms. Anyway, it became a joke to type "CListCtrl" into the text answer for a poll.
Many people now think it isn't funny any more, but I suspect that CListCtrl has transcended "joke" status, and become a tradition. Traditions don't have to have a good reason, and can continue for ever more, because "it's always been done that way..."
Gavin Greig
"Haw, you're no deid," girned Charon. "Get aff ma boat or ah'll report ye."
Matthew Fitt - The Hoose O Haivers: The Twelve Trauchles O Heracles.
|
|
|
|
|
Damn! We could have told coco that the first one to enter "CListCtrl" into an unrelated poll wins a bob T-shirt. Or something like that!
we are here to help each other get through this thing, whatever it is Vonnegut jr.
sighist || Agile Programming | doxygen
|
|
|
|
|
|
As Gavin said, it's become a tradition. I've actually only used CListCtrl once, and it's a rotten control to program. But it's still nice, once in a while, to be the first to post it as an answer to a poll. Sadly, I missed the starting gate this time.
Some people think of it as a six-pack; I consider it more of a support group.
|
|
|
|
|
It was being accidentally put into the "Other" option for a couple surveys, and I thought this was funny, so I put it in a completely unrelated survey here[^]. After this is, nearly every survey for a couple months had a CListCtrl answer or something related.
Mwahahahaha!
Chris Richardson
|
|
|
|
|
I would endeavor to write code of free bugs.
Maxwell Chen
|
|
|
|
|
SET JUNKMODE = ON;
Code against the discrimination of little, colourful animals!
Freedom for bugs!
Come on, bug-fellows, my code belongs to you!
SET JUNKMODE = OFF;
|
|
|
|
|
Ok, i was checking the optional answers to see if CListCtrl made its way in and as expected, it's there.
<font=arial>Weiye Chen
When pursuing your dreams, don't forget to enjoy your life...
|
|
|
|
|
Well, perhaps that person writes GUIs, and they all require good-looking, well-functioning CListCtrl's to function properly.
"Fish and guests stink in three days." - Benjamin Franlkin
|
|
|
|
|
Sometimes, it seems that CListCtrl has superseded 42
|
|
|
|
|
Navin wrote:
Well, perhaps that person writes GUIs, and they all require good-looking, well-functioning CListCtrl's to function properly.
Are you admitting that you are the one who enter this vote?
<font=arial>Weiye Chen
When pursuing your dreams, don't forget to enjoy your life...
|
|
|
|
|
Sounds like all are equally important. At the end of the day, it's how much time you're given that decides what you can deliver in a given time frame.
Norman Fung
|
|
|
|
|
|
Solo projects.
But I agree with you.
Tim Smith
I'm going to patent thought. I have yet to see any prior art.
|
|
|
|
|
Yes. Anything written in Prolog.
Some people think of it as a six-pack; I consider it more of a support group.
|
|
|
|
|
Daniel Turini wrote:
Is there code that is maintainable, but not understood by others?
Absolutely.
The code I write is very easy to maintain. If I'm the guy maintaining it. Add another body to the mix and things become a little more interesting.
cheers,
Chris Maunder
Remember that a lone amateur built the Ark. A large group of professionals built the Titanic.
|
|
|
|
|
While I voted for maintainable code, I am surprised that very little have voted for fast code. It would be my #2 selection.
Fast code is pretty damn important; think about it: what do you hear more often?
"Wow! This thing is fast as Hell!"
-or -
"Why the Hell is this damn thing so slow?!?"
Remember, it is often not the computer is slow, it is that the software is slow/bloated.
Peace!
-=- James
Tip for SUV winter driving survival: "Professional Driver on Closed Course" does not mean "your Dumb Ass on a Public Road"! Articles -- Products: Delete FXP Files & Check Favorites
|
|
|
|
|
Fast code, like
Wow, this thing crashed fast as hell!
?
|
|
|
|
|
i think u right, fast code is not the all of program ....
slow programing languages like VB can do more than VC++ in small project bcoz of its eazy maintainable code ...
|
|
|
|
|
Anonymous wrote:
slow programing languages like VB can do more than VC++ in small project bcoz of its eazy maintainable code ...
What crap. Anyone can f*** up a project in any language. VB isn't any easier to maintain than any other HLL.
Jeremy Falcon
|
|
|
|
|
But today, speed is decided in overall design and choice of algorithms, not in "code".
we are here to help each other get through this thing, whatever it is Vonnegut jr.
sighist || Agile Programming | doxygen
|
|
|
|