hey plzz help me its urgent

I don't consider assembler a programming language. To me, it is just a set of mnemonics.

So, in this case C is most probably the first language. And the first language normally takes a lot of time to learn and understand. Especially pointers, arrays, and the importance of evaluation order.

When you do know n languages, where n is starting to get big, then even "strange" languages will have pieces that are similar with the already known languages. The first functional language will feel strange, but the second or third will just be different writings of known concepts.

In this case, the big value with knowing assembler is that it helps with pointers, and it helps with understanding what SFR are and what makes a processor tick. Knowledge of assembler also allows the user to realize why a trivial C source line may expand into a large number of assembler instructions, or into function calls to helper functions. It is so easy to think that a source code line that looks trivial really is trivial for the processor. There should be a law that every programmer has to implement a division routine in assembler - especially since all that code represents a single little forward slash character in the HLL.

I don't consider assembler a programming language. To me, it is just a set of mnemonics.

So, in this case C is most probably the first language. And the first language normally takes a lot of time to learn and understand. Especially pointers, arrays, and the importance of evaluation order.

When you do know n languages, where n is starting to get big, then even "strange" languages will have pieces that are similar with the already known languages. The first functional language will feel strange, but the second or third will just be different writings of known concepts.

In this case, the big value with knowing assembler is that it helps with pointers, and it helps with understanding what SFR are and what makes a processor tick. Knowledge of assembler also allows the user to realize why a trivial C source line may expand into a large number of assembler instructions, or into function calls to helper functions. It is so easy to think that a source code line that looks trivial really is trivial for the processor. There should be a law that every programmer has to implement a division routine in assembler - especially since all that code represents a single little forward slash character in the HLL.

Trevor: Yes, sticky threads would be nice. But we are just end users, so we would not be allowed to edit them, or make them sticky.

Keil already have their own way to handle common questions. They have a number of FAQ pages that contains links to one or more forum threads that does cover the specific question. But it requires the users to use the search function, and a lot of Keil visitors have a policy that search engines must not be used.

Which, of course, also defeats the object of "Sticky" threads...

:-(

One thing that would be useful, though, is an easy way to get a link to an individual post - rather than just entire threads...

uk.youtube.com/watch