DISQUS

Happy Birthday, Paul. Hope you are having a good day.

I know I'll be buying the iPod touch this month, that's for sure. I absolutely fall into the "I'm not willing to pay the ridculously high price (device, setup fee, and contract for 24 months) for an iPhone but I'd love a handheld device like this". Having had my old 5G iPod stolen a year ago this is the perfect opportunity that I've been waiting for to replace it: the wireless feature is fantastic. Shame it doesn't have mail.app, but I guess GMail will have to do for now.

Eeek - why would you do this ;)?!

Seriously, I actually really like Safari 3 on Mac OS - they seem to have fixed a bunch of rendering issues, and I hate the non-native interface of Firefox even though ti is possibly the better browser.

(On second thoughts, better leave that sleepimage where it is - it's apparently a placeholder for the safe sleep image, not necessarily the image itself.)

What a cool little app! Thanks for posting about it. I have a fair old whack of disk space left yet, but I found a sleepimage taking 2gig that must've been left behind, and that I'd forgotten to empty my trash, which had about 4gig in it :).

Ah I see. It precludes you from determining the answer statically, is all I meant (i.e. you can't just have a tool that looks at the code and figures it out). It can of course do it in the way you describe.

Since JavaScript has closures, I think it's impossible to compute (though may be wrong). You could do it dynamically (i.e. run the scripts for a long time and see what happens) but it's not guaranteed to be correct. You could also get a conservative approximation using standard algorithms.

I think this is correct to some extent, but as with most rules, the best coders, IMO, know when to break them. I'd probably re-define this to say "only have well-known and obvious return points".

When tidying up some code that had seriously evolved beyond its original purpose recently, one of the most useful and important things I did was consolidate and audit the return and exit paths, and make them sane and obvious. This really helped the clarity of the code.

Nice :-).

I'm fairly unimpressed - they've even got one of their main screenshots showing a bug in the spreadsheet application (notice that the row buttons are lines up with the rows...).

Eek, that didn't look so good - not sure how to get in this message board.

The filter operation is quite cool - Python has something identical.

I'm not sure if javascript also has them, but a couple of other useful Python functions on sequences are map and reduce, which behave like:


def map(fn, list):
newlist = []
for item in list:
newlist.append = fn(item)

def reduce(fn ,list, initial_arg = None):
if initial_arg:
val = initial_arg
start = 0
else:
val = list[0]
start = 1

for i in range(start, len(list)):
val = fn(val, myseq[i])
return val


I may have goofed these up as I did them off the top of my head, but hopefully you get the idea.