Hacker News Reader

> 3. Give the developers ultimate freedom and let them do whatever they want. If the compiler never complains, beginners are happy... Example: C.

This leaves me wondering how the author would classify assembly or machine code.

View on HN

> This leaves me wondering how the author would classify assembly or machine code.

If you want to go in this direction, I'd suggest writing 1's and 0's. Can't go wrong there :-)

Btw, I actually am writing some assembly. So far I've found it very permissive (and that bit me hard).

> I actually am writing some assembly. So far I've found it very permissive

Were you expecting otherwise?

I didn't have much expectations, as I am doing it first time. But yes, I was hoping for a bit more hand-holding from asm utils. I've set wrong asm dialect and nothing detected that. Not the kind of friendliness I like.

I think assemblers won't have that sort of protection because they don't assume you're going to run on the same arch as your build.

It wasn't different then the one I was running on, it was different then I had code for. And it compiled. So either asm dialects have subtle differences that change semantics but not form, or asm silently ignores errors.

Reply on news.ycombinator.com