The MASM Forum Archive 2004 to 2012

Project Support Forums => GoAsm Assembler and Tools => Topic started by: jorgon on April 19, 2009, 05:36:03 PM

Title: New "Go" tools versions
Post by: jorgon on April 19, 2009, 05:36:03 PM
I have now uploaded to the Go tools website (http://www.godevtool.com) all the latest "Go" tools versions, previously published in bits and pieces on this site (with the exception of the latest GoLink).
The latest version numbers are:-
GoAsm Version 0.56.6
GoRC Version 0.90.4
GoLink Version 0.26.10

I have also added all these to the latest EcGo.zip file for use with the Easy Code IDE.
Title: Re: New "Go" tools versions
Post by: donkey on April 20, 2009, 01:47:14 AM
Works great, thanks Jeremy.
Title: Re: New "Go" tools versions
Post by: UtillMasm on April 20, 2009, 04:52:59 AM
C:\GoASM\Bin\GoLink.EXE  "Help2 Viewer.obj" "Help2 Viewer.res"

GoLink.Exe Version 0.26.10 - Copyright Jeremy Gordon 2002/9 - JG@JGnet.co.uk
Output file: Help2 Viewer.exe
Format: win32 size: 84,480 bytes

Make finished.

That strange character still alive. :red
Title: Re: New "Go" tools versions
Post by: donkey on April 20, 2009, 05:09:20 AM
Hi UtilMasm,

It is the UTF-8 BOM, when shown in ANSI that's how it looks. The output is probably encoded in UTF-8, the BOM is used to indicate the encoding type (since UTF-8 has no byte order issues) and the editor you are using should ignore it as does the CMD window. RadAsm will print the BOM since it does not expect format markers in the output from the pipe. This is not a bug in my opinion but an example of the robust programming we are all used to from Jeremy and GoAsm, allowing any editor to know the encoding of the character output regardless of what it is expecting. As an example you can pipe the output to a text file and view it in notepad, the characters are still there but ignored so they are not displayed.

Edgar
Title: Re: New "Go" tools versions
Post by: UtillMasm on April 20, 2009, 05:38:29 AM
I look in the output again.
the strange character is 'EFh BBh BFh' 3 bytes!
these 3 bytes is 'UTF-8 signature' right or 'UTF-8 BOM'?
is so, i think UTF-8 can need signature or not need.
i need a golink option or switche to disable generate signature, becasue i need it compatible with RadASM.
Title: Re: New "Go" tools versions
Post by: donkey on April 20, 2009, 05:44:30 AM
Hi UtilMasm,

I have been using GoAsm with RadAsm for many years, I wrote the very first GoAsm implementation for RadAsm, and have never had a problem with the BOM, after all the only thing that Ketil does is pipe the output to a text window, there is absolutely no compatibility issue at all.
Title: Re: New "Go" tools versions
Post by: Mark Jones on April 20, 2009, 07:18:48 PM
Great work Jeremy, thanks as always. :U
Title: Re: New "Go" tools versions
Post by: 1rDirEctoALgran0 on April 25, 2009, 09:18:57 AM
Hi UtillMasm,

the best thing would be that Ketil Olsen modifies RadAsm.
The output window could be printed in UTF-mode so you could use UTF characters. (And japanese characters for variable names...  :toothy)

Patrick
Title: Re: New "Go" tools versions
Post by: 1rDirEctoALgran0 on April 25, 2009, 09:27:53 AM
Another step.  :thumbu
(Don't forget to implement some FPU :eek, SSE3, SSSE3, SSE4, SSE5, ... , SSE19 :lol instructions )


Patrick

[attachment deleted by admin]
Title: Re: New "Go" tools versions
Post by: UtillMasm on April 25, 2009, 09:50:40 AM
you're right.
in fact RadASM released source code. so it's easy. and my RadASM custom version 2.2.1.2 has support GoLink's UTF-8 print.
i just suggest GoASM can do more.