flat assembler
Message board for the users of flat assembler.

Index > Main > flat assembler 1.50

Goto page Previous  1, 2
Author
Thread Post new topic Reply to topic
mike.dld



Joined: 03 Oct 2003
Posts: 235
Location: Belarus, Minsk
mike.dld
what about removing this old bug in highlighter?

Code:
mov eax,0xANY_ALPHA    
Post 08 Jan 2004, 18:37
View user's profile Send private message Visit poster's website ICQ Number Reply with quote
Tomasz Grysztar



Joined: 16 Jun 2003
Posts: 7752
Location: Kraków, Poland
Tomasz Grysztar
It's not a bug - any word starting with a digit 0-9 is treated as a number by assembler (even when it's invalid number as in your example), and fasm doesn't allow you to use it as identifier. So it's good when highligher shows you that what you have written will be treated by compiler as a number.
Post 08 Jan 2004, 18:46
View user's profile Send private message Visit poster's website Reply with quote
mike.dld



Joined: 03 Oct 2003
Posts: 235
Location: Belarus, Minsk
mike.dld
sorry but i thought it would be better to highlight it in some way [eg. red background]
Post 08 Jan 2004, 18:52
View user's profile Send private message Visit poster's website ICQ Number Reply with quote
eet_1024



Joined: 22 Jul 2003
Posts: 59
eet_1024
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.
Post 08 Jan 2004, 19:33
View user's profile Send private message Reply with quote
Tomasz Grysztar



Joined: 16 Jun 2003
Posts: 7752
Location: Kraków, Poland
Tomasz Grysztar
fasm now generates the checksum for all PE files - that might be the difference.
Post 08 Jan 2004, 19:37
View user's profile Send private message Visit poster's website Reply with quote
eet_1024



Joined: 22 Jul 2003
Posts: 59
eet_1024
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.
Post 08 Jan 2004, 20:42
View user's profile Send private message Reply with quote
mvil



Joined: 20 Sep 2003
Posts: 4
mvil
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! Very Happy
Post 09 Jan 2004, 20:16
View user's profile Send private message Reply with quote
Kevin_Zheng



Joined: 04 Jul 2003
Posts: 125
Location: China
Kevin_Zheng
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.
Post 10 Jan 2004, 07:06
View user's profile Send private message MSN Messenger Reply with quote
Dryobates



Joined: 13 Jul 2003
Posts: 46
Location: Poland
Dryobates
Kevin_Zheng wrote:
Why don't the start window show maximize?

It's not a good idea. Not all likes maximized windows (me Razz). It would be better to remember the last state. It could be stored e.g. in fasmw.ini.
Post 10 Jan 2004, 13:29
View user's profile Send private message AIM Address Yahoo Messenger MSN Messenger ICQ Number Reply with quote
decard



Joined: 11 Sep 2003
Posts: 1092
Location: Poland
decard
Actually FASMW stores last state of window (ie. its position and size) but if window is maximized, it doesn't remember it Wink I like working with maximized window, so I set its size and pos manually (that it fits the whole screen), not using "maximize".
Post 10 Jan 2004, 13:41
View user's profile Send private message Visit poster's website Reply with quote
pas



Joined: 16 Aug 2003
Posts: 17
Location: Russia
pas
What format of time received by the instruction %t
Post 18 Jan 2004, 06:26
View user's profile Send private message Reply with quote
Tomasz Grysztar



Joined: 16 Jun 2003
Posts: 7752
Location: Kraków, Poland
Tomasz Grysztar
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
Post 18 Jan 2004, 10:13
View user's profile Send private message Visit poster's website Reply with quote
mike.dld



Joined: 03 Oct 2003
Posts: 235
Location: Belarus, Minsk
mike.dld
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
}    
Post 21 Jan 2004, 09:15
View user's profile Send private message Visit poster's website ICQ Number Reply with quote
Frank



Joined: 17 Jun 2003
Posts: 100
Frank
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
Post 21 Jan 2004, 14:19
View user's profile Send private message Reply with quote
Dryobates



Joined: 13 Jul 2003
Posts: 46
Location: Poland
Dryobates
mike.dld wrote:
(...) There are some macroses which may be done on the compiler side [yes, i mean optimization], eg.

macro mov arg1,arg2
(...)


It is not good idea. Someone who will start programming in asm could think, that eg. mov es, ds is valid instruction.
Post 21 Jan 2004, 14:21
View user's profile Send private message AIM Address Yahoo Messenger MSN Messenger ICQ Number Reply with quote
Display posts from previous:
Post new topic Reply to topic

Jump to:  
Goto page Previous  1, 2

< Last Thread | Next Thread >
Forum Rules:
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Copyright © 1999-2020, Tomasz Grysztar. Also on YouTube, Twitter.

Website powered by rwasa.