flat assembler
Message board for the users of flat assembler.
Index
> Compiler Internals > EXPRPARS.INC/fp_before_dot: |
Author |
|
revolution 29 Oct 2011, 20:29
ouadji: Try using a debugger to step through and see just what byte is being skipped over.
|
|||
29 Oct 2011, 20:29 |
|
ouadji 29 Oct 2011, 21:01
it's already done Would it be reasonable to make a comment like this without checking with a debugger? no flags change, no registers change. For me, "mov al,[esi]" is completely useless. |
|||
29 Oct 2011, 21:01 |
|
revolution 30 Oct 2011, 00:10
So maybe that is the point, to allow a user in a debugging session to see the upcoming value?
Anyhow, yes, it appears to be useless, but it causes no real harm. Most probably a hang over from some previous code that has since been changed. I really don't see the point of being so pedantic with the fasm code. Tomasz already stated some time back that he views it as an artistic expression in addition to the pure functional necessity. |
|||
30 Oct 2011, 00:10 |
|
ouadji 30 Oct 2011, 09:13
Quote: to allow a user in a debugging session to see the upcoming value? Quote: he views it as an artistic expression in addition to the pure functional necessity. Joking aside, yes, a program is also an expression of oneself and therefore an artistic expression. It's obvious. |
|||
30 Oct 2011, 09:13 |
|
Tomasz Grysztar 30 Oct 2011, 09:52
No, there was no artistic thought in leaving this instruction there. As revolution suspected, it's something that was left from the previous version of the code where it was actually needed, and since it does not cause any harm it was then forgotten. There are probably more things like this in fasm sources, considering how many times each part was revised during the 12 years. In fact, it would be interesting to find out if there is any piece of code that is still unchanged from 1.0.
|
|||
30 Oct 2011, 09:52 |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.