flat assembler
Message board for the users of flat assembler.
![]() Goto page 1, 2 Next |
Author |
|
edfed
it is really a good idea.
but i'll prefer with the space. Code: dd 00 23 43 34h,32432h,233,label1 for ease of use. only one space admitted, and of course the possibility to write numbers normally without bugs. $ 1 000 000 baby! or $ 1_000_000 baby note that on french keyboard, the _ char is not practical (8 lowcase) and the space bar is good because it's a reflex. note that numbers shall be shifted on the azerty keyboard too. then, it's not a reference.. ![]() edit: it is a very_very_very_good_idea. but i really prefer with space chars. maybe the twice possibilities. wiull increase readability. Code: dq 3223_4344 4322_4334h and can be at any positions too. only one separator allowed between chars. ' ' or _ Last edited by edfed on 02 Apr 2008, 02:57; edited 1 time in total |
|||
![]() |
|
revolution
edfed wrote: but i'll prefer with the space. Code: push 123 456 ;<--- one push or two??? |
|||
![]() |
|
edfed
ok, but, i never push immediates. the stack for me is only for temp saves of context. like task switch.
then, as you want. with _ i'm ok but it will be boring on french keyboard. about multiples push and pops, i frequentlly have the reflex to make this Code: push eax,ebx,ecx and when i compile, i meet errors. in my own ( not the best) logic, the comma would be better to separate push and pop arguments. Last edited by edfed on 02 Apr 2008, 03:02; edited 1 time in total |
|||
![]() |
|
revolution
edfed wrote: ... but it will be boring on french keyboard. |
|||
![]() |
|
edfed
if i enter a number, then, i shall press the shift key.
and for each _ chars, i'll release the shift. it's a loss of comfort. that's all. |
|||
![]() |
|
revolution
For the English KB it is the opposite. Numbers are unshifted and the underscore is shifted minus (-).
|
|||
![]() |
|
edfed
so, then, it will be the same comfort problem for everybody...
[offtopic] maybe we need to change radically the keyboard layouts??? |
|||
![]() |
|
bitRAKE
RotAsm has this feature.
|
|||
![]() |
|
revolution
edfed wrote: only one separator allowed between chars. Example: Code: dq 01110110_01101000__11010110_11011001___11010010_01001101__11110110_11000000b |
|||
![]() |
|
MCD
This is an awesome idea I had several years ago and rejected it for some reason I don't remember right now.
Tomasz, are your development tools all restored by now? do you think you can manage to add this feature to fasm expression parser? btw. do you actually still have the overview of your own code when you change something in fasm? ![]() revolution wrote:
to me, this looks like an inch subdivision. _________________ MCD - the inevitable return of the Mad Computer Doggy -||__/ .|+-~ .|| || |
|||
![]() |
|
vid
edfed: idea with space is *bad*, it makes it impossible for FASM's tokenizer to tell two number from one.
I think HLA also has this, and |)rHyde uses it a lot ![]() |
|||
![]() |
|
edfed
yes, i'm sorry.
me too in my command line i have space to separate numbers. but it was just to debate. and fix some ideas. for the multiple separators, yeah. it makes a great sense and give to numbers an interresting syntax. |
|||
![]() |
|
DOS386
.
revolution wrote: Code:
dq 1000100100111000100011100011001000001100100001000101011010001011b
I prefer apostrophes: Code:
dq 1000'1001'0011'1000'1000'1110'0011'0010'0000'1100'1000'0100'0101'0110'1000'1011b
edfed wrote: Quote:
NO. The main problem is that your KBD is messed up. It's incredible how someone can type if you must press SHIFT for numbers, or even worse use the ALT-blah hack for brackets, blackslash etc. ![]() |
|||
![]() |
|
edfed
i totally agree. i seek an explanation to azerty. and finally, i don't find any as well as for qwerty..
keyboard would be much simpler with abcde. but in the old ages of type machines, this great and wonderfull industrial revolution, some theoricians emit the layout, probably they argue with some freud theory... but as a result, informatics seems to be an obscure science to when you see the keyboard for the first time. i tryed to change it's layout to abcde, and i didn't find it harder to type. the letters are in places where your hand don't need to travel a lot. if only my endglish wasn't so poor, i could explain more preciselly what i have in mind... OK for 0000'0000'0000'0000h but one extra can be added then, " and ' this will be good. but i think " and ' will be usefull later for an other purpose, like time and angles definitions. |
|||
![]() |
|
revolution
edfed wrote: but i think " and ' will be usefull later for an other purpose, like time and angles definitions. |
|||
![]() |
|
edfed
no, for strings, these symbols are only at the start and the end.
then, you seems to be tired revolution... i'm not used to see this kind of posts from you, look: Code: db 'string' dq 9543'3232'FFFF'098Ah then, you see it don't have concequences on the parsing. exactlly as the &, < and > chars can be defined alone without the need of special definition in a good html parser. then, for time and angle definitions: Code: dd 12"56'21s ; s like time in seconds ; and maybe dd 32"12'4r ; r like andle in radians??? |
|||
![]() |
|
revolution
We need to leave the quotes as quotes only, for error checking. In a macro we might use # the try to join a string to a number by mistake.
|
|||
![]() |
|
edfed
ok. then, if i want this feature, i just have to emancipate and write my own assembler. but i cannot now, i'm not so good.
then, as you're more aware of the totality of the fasm core, you are more able to decide what will be the correct form, then, _ i'm still ok. but one detail: quoted strings can be indifferentlly enclosed by " or '. then, it can be Code: "'" or '"' |
|||
![]() |
|
rugxulo
edfed wrote: depending on what is the content of the string. it don't create problems anymore. But you can also do this (borrowed from TASM): Code: msg db 'Hello, ain''t life grand?$' P.S. Octasm and Ada (EDIT: and NASM!) allow underscores, IIRC. Last edited by rugxulo on 14 Apr 2008, 23:26; edited 1 time in total |
|||
![]() |
|
Goto page 1, 2 Next < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2020, Tomasz Grysztar. Also on GitHub, YouTube, Twitter.
Website powered by rwasa.