Hi Privalov,

Thanks for the latest release,I will try it.

Hi again!

Thanks, Privalov... With the newest release, everything worked fine! Excellent! Keep up the good work!

Regards,
Tommy

Privalov,John Found, Anyone?

I would like to modify the source for fasmw to support this new feature? What do I need to change?

Simply change compiler core files and try to compile. There will be some errors because of missing variables. Add them (I can't remember exactly, but resource_size and resource_data, or similar) to the other variables and it should work.

Regards.

JohnFound,

Thanks I got it . It took a while to figure out which file the variables were supposed to be declared in but I found it eventually . Anyone who wants to update fasmw, copy all the inc files from the source directory of the package uploaded by privalov to the source directory for fasmw. Then add the code below to the data section of the fasm.inc file in source\win32\fasmw. Then compile away

Hi Ody,

Just ran a compile. Works fine. Thanks for the info.

Regards,
Art

No problem art, maybe this is tbe beginning of many more modifications to the fasm source

oh, sure same here. i'm starting tinkering with the source too.

May be i'll spin out some features for it: A tentative list of what's needed:
1. Inbuilt resource compiler (not resource inclusion).
2. Not sure if FASM supports name mangling, but will check that. Aids generation of prototypes for masm and next steps.
3. Optional parameter checks that will enable fasm to use MASM32 incs, which will also turn on libs.
4. Inline strings for Windows programming. (haven't given this much thought read it on the GoAsm board.)

Fasm's syntax is the best i've seen until now, so that's fine until somethin pops up in my head.

Regards,
Art

No need for resource compiler with fasm. You can create resources manually or use macros provided



You can do this with the invoke macro in the win32ax include files. For example you can create a messagebox like this :



I have an idea of my own. Includelib and inludeobj directives. With these there'll be no need for an external linker

i kinda tend to not use macro code that I haven't written since I don't know the things going on under the hood. If i'm not wrong, macros need expansion at assembly-time and take some more time than in-built constructs. Anyway, thanks for the comments, I'm new to FASM and i'm definitely learning a lot.

Yeah, Includelib and Includeobj sound cool. If FASM becomes capable to handle MASM stuff, I'll kick MASM away forever in the gloom of darkness.

Regards,
Art

MASM stuffs like?

only time can tell that? i'm human.

Cheers roticv,
Art

You are wrong a little. FASM uses some different approach to process macroses. There was short manual about the internal structure of FASM. Search the board for it.

Regards.

Hi JohnFound,

Thanks for the answer, anyway. Ha. Now that you've told me FASM does macro expansions in a slightly different manner, I'll get on with the internals.

Hi Art,

You can try my inc2inc tool - Masm to Fasm function prototype converter.

http://board.flatassembler.net/topic.php?t=588

Plus, have a look at my scanner tool,it declares external functions with mangled names. (Examples in the attachment :Fasm+MS link direct/indirect)

http://board.flatassembler.net/topic.php?t=72

The scanner tool is great, I use it all the time . I have another idea though. Vortex, how about adding an option for adding the functions directly to the asm source instead of a separate imp file.

There's another alternative to external scanner.

Why don't you incorporate it into FASM itself. That way, fasm will be able to use masm incs directly too. Of course, that should be optional.

Regards,
Art

Well I'm not sure about fasm itself but it would be very nice feature for fresh or the fasmw IDE. Just click scan and it creates an import section for the app with only the functions used. I like this idea. If no wants to do it I might try it myself with fasmw

art_sands: The can-opener that is also the hammer at the same time, isn't a handy can-opener, and isn't a good hammer either. It's possible to make some external compiler that could process any source you can image into fasm's source, but it's not the task of fasm itself. I have always tried to keep its set of features as small as possible - so you wouln't have to learn too much of sophisticated commands - while making them powerful enough to deal with many different problems. I propose you to dig deeper in the capabilities of fasm's macros - please appreciate all the work I've dedicated to it.

Privalov,

I LOVE FASM! If that's what you want, you got it. I feel the same way for FASM as everybody else does. It's a gem and should evolve consistently.

Regards,
Art