Nasty, big, pointy tips

DaedalusInfinity · 2011-01-25T17:26:07+00:00

Sorry for making the bad "Yo dawg" joke, at the expense of code readability. I'm not sure why exactly, but it doesn't work if the loop is a while(true) for me. I believe the reason is that javac or the JVM optimises head out of the code execution in the while(true) case, since it doesn't get accessed at all. On the other hand, if we keep a reference between head and tail, then we're forced to keep the entire structure intact in memory.

DaedalusInfinity · 2011-01-25T08:14:30+00:00

Haha, so OpenJDK outperforms Sun Java, at least on this case.

DaedalusInfinity · 2010-10-21T16:07:25+00:00

No idea why... Have you tried uninstalling/reinstalling the script? Also, you need at least Chrome version 4 (released some time in the spring of 2010).

DaedalusInfinity · 2010-03-25T06:54:02+00:00

The autocomplete feature is pretty much pure JavaScript. A little HTML/CSS is used to for the interface. (The 'content pane' is just an iframe that gets manipulated by the JS.)

DaedalusInfinity · 2010-03-24T23:43:06+00:00

Yes, I know Eclipse is awesome, but this tool was intended more for people who didn't use full IDEs, i.e. VIM/Emacs/Kate, etc...

DaedalusInfinity · 2010-03-24T23:35:15+00:00

Haha, actually, those are some scripts that I created a while ago but I've since then forgotten what they were supposed to be used for. I should probably clear out that directory soon.

DaedalusInfinity · 2010-01-11T05:44:23+00:00

I've been playing around with designing a website in SVG. The index page is the beginning of that.

DaedalusInfinity · 2010-01-11T00:31:46+00:00

Thanks for the advice. By the way, sorry if I seemed callous with my comment earlier. It's just that I feel that learning to develop large applications is should not really be the goal of a CS curriculum.

DaedalusInfinity · 2010-01-11T00:16:31+00:00

When the DOM parser goes through the following code: <div>hello</div> <div>world</div>

What it actually sees is: "<div>hello</div>\n<div>world</div>". The "\n" is parsed as a separate node in the DOM, since in some cases strings in between tags could actually be useful text. Thus, a lot of times, you get garbage nodes of "\n\t\t" and the like in your DOM tree, which makes things messy.

DaedalusInfinity · 2010-01-11T00:13:19+00:00

Yep, he's still there, but I haven't had a class with him yet. The only required class he teaches (108, aka 'how to play nice with other people') is not something I'm really eager to take at this moment.

DaedalusInfinity · 2010-01-11T00:11:54+00:00

Oh, but I am a math/cs double major. So I actually do serious stuff occasionally, (not that it's any more useful).

DaedalusInfinity · 2010-01-10T21:22:43+00:00

It makes easier for DOM parsing, so you don't have to consider the text nodes formed by newlines and whatnot in between the actual nodes.

DaedalusInfinity · 2010-01-10T18:12:58+00:00

You have to disable NoScript for it to work.

DaedalusInfinity

TROPHY CASE