qwph

14 ms·

91.
by qwph 18y ago
If that's the kind of thing that makes you feel dirty, I might suggest turning your computer off, and going out drinking...
92.
by qwph 18y ago
Firefox 3 is reported to use less memory than Firefox 2, but I've not been able to prove that myself.
93.
by qwph 18y ago
I think I might give this a go over the weekend, if circumstances permit...
94.
by qwph 18y ago
When I bought a Lenovo thinkpad, I ended up paying around $20 extra just to get XP on it instead of Vista. And it came preinstalled so I didn't get an installation disc!
95.
by qwph 18y ago
It's not fair of me to single out this particular site, but why do people insist on presenting source code in tiny little windows with both vertical and horizontal scrollbars? It makes it really hard to browse the code without copying it
96.
by qwph 18y ago
Yeah, I actually think I really like Smalltalk-the-Language - it's a really tight set of primitives which interact in a powerful way - it reminds me of Scheme or Forth. But being born and raised on the commandline, it's Smalltalk-the-Enviro
97.
by qwph 18y ago
I actually found Squeak to be a bit non-intuitive and lurid, but I have played with VisualWorks and Dolphin, to try & get a feel for Smalltalk, but I never really got my head round how things worked. Having a book handy means I have som
98.
by qwph 18y ago
This is exactly the reason any software I develop in my spare time I'd release as an open source project. I think open source also has a more attractive price tag too, but maybe I might consider selling support somewhere down the line...
99.
by qwph 18y ago
I'm currently reading a book about Smalltalk - does that count?
100.
by qwph 18y ago
I think you meant: #include <stdlib.h> #include <stdio.h> int main() { printf("true that\n"); return EXIT_SUCCESS; }
101.
by qwph 18y ago
I'm an audio programmer in the games industry. It's never been as glamourous as it sounds...
102.
by qwph 18y ago
Except that the actual compiler I was using was for the PlayStation 2, so I very much doubt it had that precise code you just outlined, and it really did have NULL defined as ((void* )0), and it really did break. I saw it happen.
103.
by qwph 18y ago
We are witnessing the Graying of Europe. You mean - people are moving around? EDIT: I just foung the phrase "Graying of Europe" to be a bit Enoch Powell, perhaps it's just me. Apologies...
104.
by qwph 18y ago
Something like that. It makes the following invalid in C++ but valid in C: int *ptr = NULL;
105.
by qwph 18y ago
I remember one early version of a C++ compiler which had NULL #defined as (( void* )0), which caused all manner of fun trying to compile some legacy C code. This was in 1999, I think.
106.
by qwph 18y ago
Let the ignorant C++ bashing begin... Speaking as someone who's spent the last 6 years maintaining large C++ applications, I'd like to think that any C++ bashing I indulged in was at least informed C++ bashing... ;)
107.
by qwph 18y ago
It was an interesting exercise. (It gratified my intellectual curiosity, you might say...) How do you suppose memory management works in high-level languages? Magic?
108.
by qwph 18y ago
There's no law that states that you have to litter your code with calls to malloc()/free() when writing C. If reference counting won't do, there's more than one garbage collector freely available, and they're not all that hard to implemen
109.
by qwph 18y ago
C always winds up with huge functions and lots of hard to grasp state up in your face. That's something I've never found to be the case. Most of my C functions are 5-15 lines long. Anything more than 20 lines long is a candidate for refac
110.
by qwph 18y ago
(Speaking as one of those people who did choose to write C over C++...) People choose C over C++ because C is a simpler language than C++, something which this new standard does nothing to address.
111.
by qwph 18y ago
Enjoyable read. I especially liked the conclusion.
112.
by qwph 18y ago
Firstly, learning more than one programming language will make you a better programmer. Secondly, you are at liberty to write code in your free time, where you can experiment with whatever language/IDE/OS combinations you deem fit. I'd ar
113.
by qwph 18y ago
For the specific example given, yes, that is true. But I think the general principle still holds.
114.
by qwph 18y ago
How about it?
115.
by qwph 18y ago
I suppose that's because it didn't result in a user-visible 404 error screen or similar.
116.
by qwph 18y ago
He also said this (I don't think he's much of an XML fan): "Structure is _nothing_ if it is all you got. Skeletons _spook_ people if they try to walk around on their own. I really wonder why XML does not."
117.
by qwph 18y ago
"Please do not place hands in path of beam."
118.
by qwph 18y ago
I guess we'll have to conclude that the "world of guitar" meanings of the terms are substantially narrower than those used by laymen. http://thesaurus.reference.com/browse/tone http://thesaurus.reference.com/browse/style
119.
by qwph 18y ago
Maybe what he means by "tone" is what you mean by "style".
120.
by qwph 18y ago
...unless you're writing code for an embedded system which has (say) 16K of RAM and a 1MHz processor, in which case that will cause you more problems than it solves.

More ›