Hi Tomasz,

(I know this most likely has been asked in the past, but a quick search of the forum doesn't yield a lot of information)...

Are you planning on building a 64bit native version of fasm? Or at least provide a thunking library between 64/32bit modes internal to fasm, so that future 64bit OSs that don't want to support 32bit code can run fasm? (Did that last part make sense)?

I haven't looked at the internals since maybe version 1.2, so are not really up to date if you've been working on making the source build natively into a 64bit object file, (with the obvious sticking points being pointers and stack access).

From another quick search of the forum: http://board.flatassembler.net/topic.php?t=5693

by the way, skip the argument of tom against rest of world (mostly me )... it's not really much releated to topic

But gives an insight into variety of opinions on this board.

please, do not leave us, 32bit board users

hehe, i wouldn't be afraid of that.. in next 2 years

Hi Guys,

Thanks for all the replys... I personally would never advocate that fasm stop being a 32bit application, just wanted to know if Tomasz had thought about migrating the main source to be both 32bit and 64bit buildable.

Thanks again.

I'm not so worried about it being 64-bit but I have been wondering when he is going to port FASM to C.

*ducks*

Of course I'm kidding

Actually Filter, I can read a exe from disk, convert it all to a string, add/subtract things from that string and then write it back to disk as an exe using javascript and ado.stream on windows.

I've always thought if only I had the time to work out all the opcodes from fasm (and of course Thomasz's cool method of multiple passes), I could make an assembler in javascript ..... wouldn't that be ridiculous

i was thinking a lot about 32 vs. 64. No doubt there is time to write support for 64bit apps. I also plan to abandon 32bit FASMLIB in few years, and rewrite it as 64bit library. New things which are gonna be future need to be supported by us.