![]() |
Easiest & Hardest Programming Language? - Printable Version +- Sinisterly (https://sinister.ly) +-- Forum: Coding (https://sinister.ly/Forum-Coding) +--- Forum: Coding (https://sinister.ly/Forum-Coding--71) +--- Thread: Easiest & Hardest Programming Language? (/Thread-Easiest-Hardest-Programming-Language) |
RE: Easiest & Hardest Programming Language? - cxS - 03-12-2013 (03-12-2013, 03:34 AM)w00t Wrote: AT&T syntax and Intel syntax represent the same thing, the difference being whether the operator or the operand should be provided first. Perhaps, but this was not what he was talking about in the first place. He was talking about the difference in the syntax, not what they represent... So I think your debate with him is irrelevant. (03-12-2013, 03:34 AM)w00t Wrote: Intel syntax, operand first: As shown by you here. And his comment here: Quote:The hardest is Assembly but there are many syntax the easiest for me is Intel syntax and the hardest is AT&T. So I'm not sure what you're trying to prove to the guy here? RE: Easiest & Hardest Programming Language? - Merkuri - 03-12-2013 (03-12-2013, 03:34 AM)w00t Wrote: AT&T syntax and Intel syntax represent the same thing, the difference being whether the operator or the operand should be provided first.Syntax 1 Spoiler: Spoiler: RE: Easiest & Hardest Programming Language? - w00t - 03-12-2013 The differences you're seeing are because you're using different assemblers, I believe NASM and GASM. The opcodes are the same, it's different representation of the same data. AT&T is just more explicit about what's going on. Use gdb to disassemble the same code, you'll see that it's the same data being represented and that AT&T does the same things, just more explicitly. Same language, different flavours. Different architectures are harder to learn, different styles of the same architecture are only slightly different. RE: Easiest & Hardest Programming Language? - Merkuri - 03-12-2013 (03-12-2013, 09:28 PM)w00t Wrote: The differences you're seeing are because you're using different assemblers, I believe NASM and GASM. The opcodes are the same, it's different representation of the same data. AT&T is just more explicit about what's going on. Use gdb to disassemble the same code, you'll see that it's the same data being represented and that AT&T does the same things, just more explicitly. Same language, different flavours. Different architectures are harder to learn, different styles of the same architecture are only slightly different. What I have said that the command are a little bit different and AT&T is harder for me by this. I'm using Emu8086 for the both. |