Hacker News Reader

Comment by pjmlp | Hacker News Reader

Partially true, because ignoring messages to nil only works with Objective-C data types, any classical C style programming will segfault as in plain C.

Just like in C++, while there are high level abstractions that avoid traditional C memory corruption issues, there are always those that insist in sticking to the C subset.

View on HN

> any classical C style programming will segfault as in plain C.

As I wrote, you wrap those in an Objective-C container that manages that pointer, and delegate the C access to that container.

So not:

    c_pointer = [container getPointer]
    <munge on pointer>

But rather:

    [container doSomeMungingOnYourCData];

Which is, of course, how you should be doing things in OO style anyhow. So that works out just fine.

But yes, some people do insist on doing things the hard, slow, nasty way. They get punished.

Reply on news.ycombinator.com