News for hackers. Stuff that matters.
Re:Glibc getaddrinfo stack-based buffer overflow by J_Darnley on Tuesday February 16, 2016 @03:06PM (#11112752)
> Can people tell me why they start projects in ... C still?

Okay. Based on my current project (Porting AVS out of shit-tier Microsoft C++). I want a region of memory in which I can treat as a bitmap and set pixels at given location to given colours. I know of no other language that gives me this block of memory to draw into. That's probably because I don't know enough. Most languages seem to tout how immutable things are. That's a big word for many people and it just means "does not change".

If other languages want my attention then maybe they need more than a "Hello, World!" and some string processing. Show me your malloc equivalent and see if I can go from there.

Re:Glibc getaddrinfo stack-based buffer overflow by GregBuchholz on Wednesday February 17, 2016 @12:00PM (#11119247)
>I want a region of memory in which I can treat as a bitmap... ...Show me your malloc equivalent and see if I can go from there.

http://www.lispworks.com/documentation/HyperSpec/Body/f_mk_a...

https://wiki.haskell.org/Numeric_Haskell:_A_Vector_Tutorial#...

Re:Glibc getaddrinfo stack-based buffer overflow by J_Darnley on Wednesday February 17, 2016 @02:46PM (#11120669)
Thank you.