HP41UC: User-Code File Converter / Compiler / De-compiler / Barcode Generator

[leoduran]

(09-25-2016 01:19 PM)Dieter Wrote:  No problems so far. And I really like the idea of adding your own XROM function set.

That's good, thanks for the feedback.

(09-25-2016 01:19 PM)Dieter Wrote:  I'm not sure if I like the appended XROM numbers the decompiler generates.

This is useful because some function names are duplicated in multiple modules, so this tells you which module was actually decompiled.

(09-25-2016 01:19 PM)Dieter Wrote:  BTW, what character set does the program support? Since it does not use "≠" or "Σ" it looks like it can handle only plain ASCII or maybe ANSI. What about Unicode? This would allow the two mentioned characters.

Here's a cut-paste from the "Importing XROM Modules" section in the UsersGuide: XROM modules may be imported from one or more ASCII text files...

(09-25-2016 01:19 PM)Dieter Wrote:  FTR: With the built-in card reader functions disabled (/x30) I tried my own card reader file with all the XROM 30, nn functions and only 7RCLS replaced with 7RCLΣ. This file was saved as "reader.txt" using Windows Notepad with Unicode encoding.

Then I tried
hp41uc /t=test /r /x30 /m=reader.txt /n /k

The result was an error message saying that no end-of-line character could be found. Then I stored the same file using notepad++ and this time the EOL-warning did not show up. Instead hp41uc did not understand the line defining the 7RCLΣ command as it could not decode the Σ character:

XROM Error: invalid arguments[ 7RCLΣ 30,35 ]

I assume fixing this is not trivial, so it may stay the way it is.

Dieter

Interesting thought on supporting unicode; but yes, it would not be trivial, and frankly IMO not necessary... Remember, function names are not part of the actual user-code encoding (as that is simply of the form XROM mm,ff). What is important is that the text in the XROM file is consistent with the text used in the program listing (function names in the XROM files simply serve as a lookup, so that HP41UC can use the corresponding 'mm,ff' ID's).

So as you alluded to, I suggest replacing HP-41 special characters with reasonably equivalent printable ASCII characters, for example: using 'S' for 'Σ', and '#' for '≠'.