Index
> Windows > DLL version of fasm |
| Author |
|
|
vid 17 Jan 2005, 21:22
yes
(too bad nobody have done it yet) |
|||
17 Jan 2005, 21:22 |
|
|
Tomasz Grysztar 17 Jan 2005, 22:39
It should be easy to adapt the FASM.INC from the FASMW to become a DLL - it can be invoked multiple times without any problem.
|
|||
|
17 Jan 2005, 22:39 |
|
|
beppe85 18 Jan 2005, 10:15
Yes, I will love it. Would be nice too if fasm.dll accepts an internal buffer instead of filename.asm.
|
|||
|
18 Jan 2005, 10:15 |
|
|
Madis731 18 Jan 2005, 13:58
WOW! You mean that is is possible to make ASM scriptable??? WOW
You can make a program that accepts plugins as ASM-code and then you can just call FASM.dll to assemble them  nice trick! |
|||
|
18 Jan 2005, 13:58 |
|
|
beppe85 18 Jan 2005, 16:01
No more than already. You can spawn FASM.exe passing the file to compile, listen to its results, and map in the output.
|
|||
|
18 Jan 2005, 16:01 |
|
|
f0dder 18 Jan 2005, 18:05
Doing in-memory operations is cleaner, and it will be faster, even if windows does a good job of caching, and has the FILE_ATTRIBUTE_TEMPORARY flag.
|
|||
|
18 Jan 2005, 18:05 |
|
|
beppe85 18 Jan 2005, 20:16
Yes, I prefer component-based reuse instead of that *nix pipes. You can do, its just a matter of taste.
|
|||
|
18 Jan 2005, 20:16 |
|
< Last Thread | Next Thread > |
Forum Rules:
|