(no subject)

I think I'm getting the point of Christian (after a few more e-mails): he's using automake, he likes it, and that's the way it is. Even if each of my makefile subparts are about as big as a Makefile.am. I'm pretty sure that if I could hack a version of automake that would produce non-recursive makefiles, he'd use it.

Anyone who's a firm believer of recursive makefiles should hack on Mozilla a bit. On my Pentium 225, an empty make (one where there is nothing to build, like if you do make twice) takes upward of 15-20 minutes! And it's nothing close to "exact dependencies".

Maybe I should do just that, hack automake to produce a single non-recursive makefile?

But I also have to hack so many other things...

Movies

I went to see Meet the Parents yesterday with my girlfriend. It's okay, but then, I loved 10 Things I Hate About You, so I guess I'm some kind of twisted, crazy moviegoer. The Whole Nine Yards is also very good, plus you get to see Montréal!

Asynchronous I/O

Linus Torvalds is a freakin' genius. I find some problem with his proposed API because of the fact that the events are edge-triggered, and I like being able to read or write only a limited amount and have the event trigger again to continue (so that all connections are given a fair chance).

Actually, that's what I thought upon first reading this, but you see, the guy is really a freakin' genius!

It's not a perfect proposal (means many system calls for binding file descriptors, if you want to rebind after every event), but it's a really good idea. The bind_event system call could be made user-space and its functionality rolled into the get_events system call, so that the next time get_events is called, it gets the events to bind/rebind, and then returns what's new.

I know there are racy problems with this last paragraph, but they could be fixed, I just don't know how (did I mention Linus is a freakin' genius?)...