Viewing profile — ehmmm

Your logical fallacy is, drum roll... : Hasty generalization Congratulations! You win nothing.

On the contrary, what? Who said anything about indie games specifically? This sub-thread is talking about modern games, all of them. My comment still stands. Games that make most o…

Most of them are burdened by graphics. It sells better.

Dead ends are there for a reason to create a sense of a larger world. They are usually blocked by some logical obstacle, and rarely actually lead to a short alternate area, but not…

Yes. And if I remember correctly, if you bomb the block, the super missile logo appears on the block.

Those mechanics are way too subtle. Today, the player must be explicitly told how to overcome obstacles. Games have become mainstream and so did the target audience, this caused a …

MAD

But Google didn't make any promises to anyone specifically. They just made a statement they will not actively sue. How will you justify that you experienced negative consequences b…

Such statements are not legally binding and thus completely irrelevant in a lawsuit.

Interesting choice. One is still able to add a module that wraps the calls with a custom allocator.

1. The current version of the library contains a profound design flaw - it allocates memory. What do you mean by that?, or could you elaborate how will you design it to not allocat…

It is so close to full C11 support. I think just threads.h are missing now.

One her comments: well, if its over 100 mSv/h, then acute radiation sickness begins after ~2 hours (noticable reduced blood cell count from 200 mSv acute dose onward, though you'd …

Sure, &foo->bar looks like foo + offsetof(struct thingity, bar) , but there is no pointer arithmetic involved since C doesn't specify how the member access ( -> or . ) is actually …

Clearly, you don't have anything constructive to say, so you have to resort to ad hominem. [] operator doesn't have any place in this debate.

There is no pointer arithmetic in the line: struct usb_line6 *line6 = &podhd->line6; Offset is calculated "below the hood". Pointer arithmetic is defined with arithmetic operands: …

Oh I see, it moves the stack pointer so it coincides with the heap allocated memory? I like articles that combine hacking and C, but this one really needs more explanation.

Seems to be a decent warning to security experts on how are you going to be treated in such situations, and a remainder to act accordingly.

Can you elaborate on that. It doesn't seem to work correctly on my machine. Writing beyond heap bounds and uninitialized reads.

Algorithm is not the same as the the source code, which is what genes contain. We have obtained them trough gene sequencing, but we still don't know how organisms work and grow.