Index
> Macroinstructions > Help with a NASM -> FASM macro conversion |
| Author |
|
|
VitalOne 18 Jan 2004, 19:54
I'm not sure what the macro exactly does but here's what I've got:
Code: macro code arg1 { arg1: } So now you could do code start or something. |
|||
18 Jan 2004, 19:54 |
|
|
VitalOne 18 Jan 2004, 19:56
To make it easier for conversion, this also does the same:
Code: macro code 1 { 1: } |
|||
|
18 Jan 2004, 19:56 |
|
|
crc 19 Jan 2004, 04:48
Thanks for your help. The macro you supplied works perfectly for what I needed to finish the port of SEDForth to FASM. While there are a few (minor) problems left to fix, it compiles the handful of small test programs easily now. I've attached a copy here for those who want to look at it.
|
|||||||||||
|
19 Jan 2004, 04:48 |
|
|
ronware 19 Jan 2004, 06:15
crc wrote: Thanks for your help. The macro you supplied works perfectly for what I needed to finish the port of SEDForth to FASM. While there are a few (minor) problems left to fix, it compiles the handful of small test programs easily now. I've attached a copy here for those who want to look at it. Excellent! I am porting RetroForth, and I want it to work on both Windows and Linux. Cool... |
|||
|
19 Jan 2004, 06:15 |
|
|
crc 19 Jan 2004, 06:37
Well, porting RetroForth over will be a much larger task than porting SEDForth (which is why I started with a SEDForth port). As far as I know, you'll have to redo the entire dictionary macro system, a big pain since it is heavily dependent on NASM's xdefine macro functionality. I'll help where I can once I finish the 6.20 release (which brings a lot of cleanups to the core codebase). If you can get RetroForth ported over to FASM, please share the source - I'd love to see it
 |
|||
|
19 Jan 2004, 06:37 |
|
|
ronware 19 Jan 2004, 06:46
crc wrote: Well, porting RetroForth over will be a much larger task than porting SEDForth (which is why I started with a SEDForth port). As far as I know, you'll have to redo the entire dictionary macro system, a big pain since it is heavily dependent on NASM's xdefine macro functionality. I'll help where I can once I finish the 6.20 release (which brings a lot of cleanups to the core codebase). If you can get RetroForth ported over to FASM, please share the source - I'd love to see it I am at the point where I have an executable which crashes 
But I think it should be pretty soon... (if I didn't have lots of other things to do, like paying work |
|||
|
19 Jan 2004, 06:46 |
|
|
crc 19 Jan 2004, 07:35
Quote: I am at the point where I have an executable which crashes If you send me a copy of the code you've got, I'll see if I can help you get it working. I have a decent amount of free time right now. If you've already got it to assemble you're doing good! Congratulations on your current progress. |
|||
|
19 Jan 2004, 07:35 |
|
|
ronware 19 Jan 2004, 18:21
crc wrote:
I sent you a copy via email - I didn't want to post something half-baked on the board. Thanks, and all the best. |
|||
|
19 Jan 2004, 18:21 |
|
< Last Thread | Next Thread > |
Forum Rules:
|