In a new processor/language definition, is it possible to change the hex sigil from $?

[hippietrail]

I'm experimenting with Ghidra for the old TI-99/4A, which used > instead of $ as the hexadecimal prefix in both TMS-9900 assembly language and its GPL (Graphics Programming Language) assembly language, which is for a byte-code used extensively on the machine.

Is it possible to change the hexadecimal prefix string for a language?

If not, which source code file(s) in the source are responsible for rendering integers in the disassembly listing? Is it part of the Sleigh system? Or does that system just supply numbers that a higher-level component renders? I'm guessing it's in the Sleigh code since other parts of the assembly code can be rendered from string literals in the .slaspec files.

It's hard to search for, so perhaps somebody knows the code well enough to point in the right direction.

[GhidorahRex]

I assume you mean for instruction operands? We don't normally use $ as a prefix string for hex literals. We use 0x. Ghidra does not allow customization of this prefix (or suffix in the case of FFFFh).

The code responsible for the listing display is in Scalar.java on line 286. But I can't guarantee that changing that won't have weird side-effects, but that is where it is located.

[hippietrail]

Oops silly me. I should've double checked before writing from memory. But now I noticed that while my very experimental TI-99/4A GPL processor does show 0x prefixes for hex, my experimental Apple Lisa loader is showing h suffixes for hex..

0x prefix:

h suffix:

Silly me again. I should've read your message more thoroughly before replying. I'll look at Scalar.java and thank you.

[GhidorahRex]

Data is handled differently than instruction operands (notice how the operands in the Apple Lisa are still prefixed by '0x', only the data has the suffix).

[hippietrail]

The code responsible for the listing display is in Scalar.java on line 286. But I can't guarantee that changing that won't have weird side-effects, but that is where it is located.

I'm investigating what it would take to implement this. So just noting here that the two main places with code responsible for the h suffix are DefaultDataType.java and AbstractIntegerDataType.java. The latter is for fields of structs.