26 Jan 2008 (updated 26 Jan 2008 at 04:44 UTC) »
mchirico, redi: what you can try to do is to put your link in the article talk page, and ask an independent administrator (hopefully one who's not an insane idiot) to look at it and give the go-ahead to put it in. If nothing happens, maybe put up an RfC to blow up the whole matter.
This is even in the Wikipedia policy text, but I guess most of the administrators can't be bothered to point it out because they're more concerned with how to make Jimbo Wales look good in the wake of the Essjay incident.
3 Jan 2008 (updated 3 Jan 2008 at 11:03 UTC) »
As fzort said, I (or rather we) patched a coroutines library for C so that it'll compile on newer gcc's, and I e-mailed the patch to the maintainer.
Since I've not received any response yet, I decided to upload it to my web page.
9 Nov 2007 (updated 9 Nov 2007 at 11:45 UTC) »
I rewrote the patch to use ccg instead of froofyJIT (to take advantage of being able to directly write x86 code), and posted the new patch on the timidity-talk mailing list. First response:
Does it work on the x86_64?
Oops. Um... no, not really. But thanks for asking.
24 Sep 2007 (updated 27 Sep 2007 at 15:11 UTC) »
I released froofyJIT 0.26.
Also, I experimented with using froofyJIT to speed up TiMidity++ -- profiling revealed that when processing Rakhmaninov's G minor prelude, it was spending ~1/4 of its time in do_ch_freeverb(), which is static optimization hell. After some hacking, here's the result: a tidy big patch which reduces the running time on this file by ~4%.
The patch probably isn't suitable for the TiMidity++ mainline though, especially since it's in C++, while the rest of the TiMidity++ code is in ye olde C.
Update: the patch is now stashed in the froofyJIT 0.27 tarball.
20 Sep 2007 (updated 20 Sep 2007 at 20:22 UTC) »
Mozilla may soon have... a JIT compiler for JavaScript? (!) I guess that means JavaScript is well on its way to becoming a Real Language™ (if such a classification makes sense).
6 Sep 2007 (updated 6 Sep 2007 at 10:06 UTC) »
Follow-up on the JavaScript font rendering effort:
fzort informed me that the glyph rendering was bogotified on Internet Explorer:
After more than half a day of hacking, I finally managed to stop IE from rendering the extra stuff below each glyph, and work around IE's PNG transparency bug... and in the process I also learnt about the clip: rect(...) CSS property. :)
Here's the result.
MarkAtwood: Who exactly wrote that, and where exactly did he write that? I hope it's not another of those "let's attribute this fake quote to some famous luminary" things.
FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!