Index
> Compiler Internals > Case of the names |
| Author |
|
|
revolution
So you want to make names case-insensitive?
You could make your own version of fasm and post the changes here. You never know, Tomasz might decide it is a good idea and include it.  |
|||
29 Dec 2009, 02:03 |
|
|
bitshifter
Its quite useful.
Say we have an equate or macro in uppercase as NAME1 and then we could have a variable or procedure as Name1 also. It really comes down to coding style... |
|||
|
29 Dec 2009, 03:48 |
|
|
LocoDelAssembly
And actually it can also be used in labels. For instance, if you would like to emulate objects you could name the class "Matrix" (where the VMT, class variables and other data is stored) and then have an instance variable called "matrix" (this practice is not uncommon).
I think I have some code that would be broke by such change but well, I get no revenue from my Assembly code and nothing is used in production so it wouldn't be a very big problem for me this backward incompatibility... |
|||
|
29 Dec 2009, 04:45 |
|
|
booter
LocoDelAssembly wrote: ... you could name the class "Matrix" (where the VMT, class variables and other data is stored) and then have an instance variable called "matrix" (this practice is not uncommon). It may be useful for developer, but it makes reading the program text a nightmare. BTW, I also dislike labels like that "I1lO0OrnmVVW"  |
|||
|
08 Jan 2010, 00:36 |
|
|
LocoDelAssembly
Quote: That's exactly what I want to be prohibited (optionally). I like this idea, it won't break compatibility. The only problem would be to define how this feature would be enabled. I think that a command line argument won't be a problem as it probably won't break SSSO principle and forgetting to use the option wouldn't make the source uncompilable. |
|||
|
08 Jan 2010, 00:42 |
|
|
vid
It would break SSSO:
Code: a=1 A=2 db a You would get different output on same source depending on command line params. |
|||
|
08 Jan 2010, 12:21 |
|
|
LocoDelAssembly
Yep, and very simple example, I'm getting reeeeally old
 |
|||
|
08 Jan 2010, 16:10 |
|
|
r22
@booter - I totally agree about the bad style.
But style is for the programmer to decide, FASM is just easel letting you paint whatever you want on it. If you decide not to use Name1 and NAME1 then FASM won't need to enforce your decision. Enforcing code style is a HLL concept not really suitable for ASM (maybe low level programmers are too stubborn and set in their ways to conform to a widely agreed upon syntax standard), |
|||
|
08 Jan 2010, 19:50 |
|
< Last Thread | Next Thread > |
Forum Rules:
|