WARNING TECHNICAL CONTENT BELOW:
Al recently told me that the best thing about this blog lately was when I put a warning before a post about software. Well, there you go.
Yesterday I was writing a little tool in C to analyze the memory dumps from the Motorola Timeport's simulator. The simulator's VM can be told to write an entry to a file everytime it calls malloc() or free() internally while running your Flexscript program. This way, the programmer can track down memory leaks (they are FAR from obvious just by looking at the code). Unfortunately the tool they give you to detect the memory leaks just, well, doesn't seem to work. So I'm writing my own.
Anyway, in my 8 or so years of programming in C, I have NEVER fallen into the following trap ...
/* using the assignment operator instead of comparison */
if (a = b) { ... } ...
... until yesterday night. Can anyone guess WHY? It's because of months of flexscript programming, where the construct above is correct. Working at this job is actually making me a WORSE programmer! :)
BTW: Google finds me authoritative on timeport sucks and flexscript sucks. Nice!
10:31:05 AM 
|
