Larry:
Three questions.
First, when Paul provides updates to EBasic, does he include the latest NASM updates when they are available as part of the EBasic download?
The reason I ask is that I updated NASMW.exe found in the EBDev/bin folder with the latest NASMX/NASM version 2.08rc5 update for Windows. It seems to be working just fine so far.
Second question. Do you know if Paul changes anything in the NASM assembler to make it interface better with EBasic? It doesn't appear that he makes any alterations to NASMW so, updating to the latest NASM versions should be okay.
Finally, do the EBasic upgrades include the latest upgrades to GORC.exe when they become available from Jeremy Gordon's "go tools" website?
I often update both these tools and was just wondering if I'm upgrading unnecessarilly. I also assume that eLink.exe is written by Paul and is not a renamed version of MS' link.exe or Jeremy's goLink.exe.
Thanks, Logman.
I don't think he updates them.
I know I had to update the GORC to get something to compile that I was doing. Right now I can't remember what I was doing. I know sapero has posted about it.
Larry
Hi Logman.
Paul's NASM is a modified build of the 0.98 series.
The main modification is the debug symbol output for the integrated debugger additional to some vital bugfixes of that build.
In the 2.xx build are these bugs fixed as well so if you do not use the integrated debugger you can change the new NASMW.exe safely.
However you have to put sometimes "-w-orphan-labels" into the advanced/assembler options to suppress warnings.
"eLink.exe" is unique to EBasic you can not use MS Link due to the two library implementation is just so far from each other you can get.
There is a new version for "ar.exe" in "binutils" distribution as well.
Thanks Larry and Ficko for your answers.
I thought eLink was unique to EBasic. I seem to remember Paul mentioning this several times in these forums. As a result, I haven't switched to GoLink for example, I just leave it alone because it works fine.
However, I was curious about updating the basic NASM assembler because, as you suggested, it seemed to be an older version. I just didn't want to break EBasic by inadvertantly updating NASM to version 2.x. NASM 2.x seems to work smoothly and since I don't often use the built in debugger, I think I'll be okay.
I appreciate your suggestion about putting "-w-orphan-labels" into the current NASM version to suppress warnings. I didn't know this.
When I do need to use the integrated debugger, I can always switch back to the original NASM version that comes with EBasic using a simple .bat file to go back and forth.
As Larry suggested, I think I'll keep the upgraded GORC because it seems to work better and hasn't given me any problems.
Thanks, Logman.