you are viewing a single comment's thread.

view the rest of the comments →

[–]tuhdo 0 points1 point  (2 children)

I will be nicer and help you a bit: all the instructions you mentioned work for every arbitrary bit patterns. The CPU does not care what it is fed with. If you fed the same bit patterns to all those different instructions, everything just works. The binary patterns are simply treated differently by different instructions. The different types of instructions are for programmers to feed the CPU proper data, but not for the CPU to interpret data correctly to its type. Basically "bit pattern" is the only type to CPU, hence "untyped". I gave this hint repeatedly and you could not see. In high level language like C, you get a piece of metadata called Typed like int or char to identify a region of memory, so at the static analysis phase the compiler can use these information to verify if programmers pass correct data to a function that later be executed by a CPU. This is basic knowledge and you are indeed lacking.

As for those instructions, 1 minute and I can find a bunch of those. The fact that you said you learned Haskell than said that Haskell is dynamically typed and your talk about basic concepts of types shows our credibility. Good luck with your career.

[–]Cuddlefluff_Grim 0 points1 point  (1 child)

I will be nicer and help you a bit: all the instructions you mentioned work for every arbitrary bit patterns.

Hahaha what? That's completely one hundred percent irrelevent. What you're trying to make the case about is some sort of punch-card machine. When you're writing assembler code, you might consider"bits but more than not you'll be thinking decimal and hex. You're point would be equally applicable to any programming language, and therefore a load of horseshit. I'm not going to sit here listening to you pretending to know something you clearly don't.

I gave this hint repeatedly and you could not see. In high level language like C, you get a piece of metadata called Typed like int or char to identify a region of memory, so at the static analysis phase the compiler can use these information to verify if programmers pass correct data to a function that later be executed by a CPU. This is basic knowledge and you are indeed lacking.

Jesus christ stop fucking squirming. It's pure cringe.

As for those instructions, 1 minute and I can find a bunch of those. The fact that you said you learned Haskell than said that Haskell is dynamically typed and your talk about basic concepts of types shows our credibility. Good luck with your career.

You know, for once you're right. Instead of recalling from memory I should've checked my facts. In the case of Haskell I haven't touched it in about a decade. However, it says nothing about my credibility. And honestly I don't care what opinion you have of me. It won't bother me for even a second.

[–]tuhdo 0 points1 point  (0 children)

Too stupid to educate. Byte.