Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
The Origins of Malloc (spinellis.gr)
54 points by signa11 on Sept 14, 2017 | hide | past | favorite | 7 comments


This article was rather brief.


Agreed. I do like the trivia of malloc() likely being "map alloc", and free() originally being called mfree().

The article also quotes Lions, which is a fun read. You get the sense that the Unix philosophy of "everything's a file" originally had a sibling: "everything's an int".


  B is typeless, or more precisely has one data type: the
  computer word. Most operators (e.g. +, -, *, /) treated this
  as an integer, but others treated it as a memory address to
  be dereferenced. 
https://en.wikipedia.org/wiki/B_(programming_language)


And linear addresses and addressing has tons of advantages. Macroarchitecture obviously deal well with word-sized linear addresses and there's all sorts of neat speed up tricks the microarchitecture can use when the word-size can address as much or more than the memory port interface, address lines, cache address lines, TLBs, etc.


Still worth a lot to me.


This comment was rather brief.


And yet just as full of information as blog posts thrice its size.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: