flat assembler
Message board for the users of flat assembler.
Index
> Main > flat assembler 1.50 Goto page Previous 1, 2 |
Author |
|
mike.dld 08 Jan 2004, 18:37
what about removing this old bug in highlighter?
Code: mov eax,0xANY_ALPHA |
|||
08 Jan 2004, 18:37 |
|
mike.dld 08 Jan 2004, 18:52
sorry but i thought it would be better to highlight it in some way [eg. red background]
|
|||
08 Jan 2004, 18:52 |
|
eet_1024 08 Jan 2004, 19:33
Is WDM's supported under 9x, NT, or both. Will the LE format ever be supported, if needed?
I noticed the change while comparing binaries compiled with 1.49 to ones compiled with 1.50. |
|||
08 Jan 2004, 19:33 |
|
Tomasz Grysztar 08 Jan 2004, 19:37
fasm now generates the checksum for all PE files - that might be the difference.
|
|||
08 Jan 2004, 19:37 |
|
eet_1024 08 Jan 2004, 20:42
I also noticed the use of %t in the resource macros.
Let me reword my question. Can I create a driver for 9x, NT, of both OS's using the WDM format. Or is LE the only format for making a 9x (98 ) driver? I reviewed my compares, and I believe all differences are accounted for: Checksum, compile time (expected), resource dates, and the enter upgrade Can the format directive in \fasm\INCLUDE\WIN32AX.INC be conditional? I have several Win32 console programs, and I had to comment out that line in the include file. |
|||
08 Jan 2004, 20:42 |
|
mvil 09 Jan 2004, 20:16
Hey, I noticed the thread CONTEXT structure has magically disappeared from the kernel32 equates. It was there in v1.49, so I was just wondering where it went and why...
Oh, and thank you for another fine release! |
|||
09 Jan 2004, 20:16 |
|
Kevin_Zheng 10 Jan 2004, 07:06
Dear Privalov:
I have a short advice for the fasmw. Why don't the start window show maximize? I think that it maybe fit the work on. Code: ;fasmw.asm--313 lines mov [hwnd_main],eax ;Kevin Zheng[011004]invoke ShowWindow,[hwnd_main],SW_SHOW invoke ShowWindow,[hwnd_main],SW_MAXIMIZE ;Kevin Zheng[011004] invoke UpdateWindow,[hwnd_main] And others, the asmedit control shows the unicode text normally, but it can't get the unicode text. Thank you. |
|||
10 Jan 2004, 07:06 |
|
Dryobates 10 Jan 2004, 13:29
Kevin_Zheng wrote: Why don't the start window show maximize? It's not a good idea. Not all likes maximized windows (me ). It would be better to remember the last state. It could be stored e.g. in fasmw.ini. |
|||
10 Jan 2004, 13:29 |
|
decard 10 Jan 2004, 13:41
Actually FASMW stores last state of window (ie. its position and size) but if window is maximized, it doesn't remember it I like working with maximized window, so I set its size and pos manually (that it fits the whole screen), not using "maximize".
|
|||
10 Jan 2004, 13:41 |
|
pas 18 Jan 2004, 06:26
What format of time received by the instruction %t
|
|||
18 Jan 2004, 06:26 |
|
Tomasz Grysztar 18 Jan 2004, 10:13
It's the common timestamp (that is, the number of seconds since the 1st Jan 1970, 00:00), you can find an example of converting it into data and time here: http://board.flatassembler.net/topic.php?t=499&postdays=0&postorder=asc&highlight=timestamp&start=15#3163
|
|||
18 Jan 2004, 10:13 |
|
mike.dld 21 Jan 2004, 09:15
Hi, Privalov!
There are some macroses which may be done on the compiler side [yes, i mean optimization], eg. Code: macro mov arg1,arg2 { if arg1 in <eax,ebx,ecx,edx,esi,edi,ebp,esp> if arg2 eqtype [] mov arg1,arg2 else if arg2 in <eax,ebx,ecx,edx,esi,edi,ebp,esp> mov arg1,arg2 else if arg2 = 0 xor arg1,arg1 else if arg2 = 1 xor arg1,arg1 inc arg1 else if arg2=-1 or arg1,-1 else if arg2 < 128 & arg2 > -128 push arg2 pop arg1 else mov arg1,arg2 end if else mov arg1,arg2 end if } |
|||
21 Jan 2004, 09:15 |
|
Frank 21 Jan 2004, 14:19
Several of these optimizations have side-effects. For instance, a hand-coded "mov eax, 0" won't change the flags, whereas its size-optimized alternative "xor eax, eax" will. Because of the side-effects, such optimizations should not be done silently by the assembler. Instead, they are better kept in macros, where they are more visible. IMHO.
Regards, Frank |
|||
21 Jan 2004, 14:19 |
|
Dryobates 21 Jan 2004, 14:21
mike.dld wrote: (...) There are some macroses which may be done on the compiler side [yes, i mean optimization], eg. It is not good idea. Someone who will start programming in asm could think, that eg. mov es, ds is valid instruction. |
|||
21 Jan 2004, 14:21 |
|
Goto page Previous 1, 2 < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.