A painting of me

Go Data Structures. ⇒

   1 December 2009, lunch time

A good overview of how structures are laid out in memory.

This is a post from my link log: If you click the title of this post you will be taken the web page I am discussing.

Perma-Link  

Comments

  1. Have you looked into the language in-depth at all? That page in particular seems very Pascal like, which surprised me.

    I’m glad to see there are still pointers though. Can’t really do systems level stuff without explicit memory management.

  2. I wrote a multi-threaded echo test server here at work. It’s a pretty slick language, though I think it still has some work to go in terms of library support. There’s no big to little endian conversion functions too, which seems like an oversight. I also couldn’t figure out how you are supposed to translate from a set bytes to an integer — which makes having binary length headers in messages problematic. There is apparently some sort of encoding library you are supposed to use to read binary data into a structure, but I didn’t look too deeply into that. People on the mailing list said it was slow. It’s an interesting language anyway. There is some OO stuff, but it feels very procedural.

Don't be shy, you can comment too!

 
Some things to keep in mind: You can style comments using Textile. In particular, *text* will get turned into text and _text_ will get turned into text. You can post a link using the command "linktext":link, so something like "google":http://www.google.com will get turned in to google. I may erase off-topic comments, or edit poorly formatted comments; I do this very rarely.