Hey! It’s been months! What happened?
105363 items (97572 unread) in 19 feeds
Friends
(1021 unread)
Build
(68091 unread)
Heads
(716 unread)
News
(27537 unread)
fun
(207 unread)
Hey! It’s been months! What happened?
not to just chime in about another compiler a month later, but whatever.
There’s also Watcom, which used to be a decent compiler especially due to the dos/4gw extender. I think it’s been opensourced as OpenWatcom for a while, but it’s development might be dead.
I took some notes from a talk by Brett Cannon (Python core developer) at a meetup, which I hope I faithfully reproduced onto my blog:
“For performance reasons Unicode strings are stored in UTF-16 internally, but you will likely stick with UTF-8 and let Python take care of the translation.”
I’m no guru on codepoints and encodings and all, but that sounds like pretty standard fair… doesn’t Windows use UTF-16 for the same reason?
@Josh I’ve still been debating Python vs. Ruby, heh.
re: “Python will always run the entire file through a transcoder first…”
There is a byte type in Python 3, so if you just wanted to grab the length or whatnot, you could use that and skip the transcoder.
[...] Puppet: Act One.” Ruby 1.9.x is a fairly significant change. See Josh Haberman post “Ruby 1.9.1 released,” Markus Prinz post “Ruby 1.9 - What’s new? What’s changed?“, and [...]
Thanks for this article. Once upon a time (back in 2002), I gave a short overview of some hashing techniques to the Hackers-IL mailing list. Seems like I missed some stuff you mentioned here, which wasn’t covered in my introductory Data Structures and Algorithms course.
I myself, always prefer to use some form of chaining instead of open addressing. That’s because with open-addressing, it’s harder to tell when an item was removed or does not exist at all, and as a result the hash becomes much more flimsy. Maybe there’s some magic way to achieve it, but I’m still ignorant of it.