You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not emitting anonymous labels is tricky without support from RGBLINK, since they must be emitted by RGBASM to be linkable. (Hence the unique names to begin with.)
It's possible to instead skip emitting symbols whose first character is non-conformant (note that the rest can and should simply use \u escapes), I'm just not sure if that's desirable.
I assumed this would be a feature of rgblink only, since it outputs the .sym files. That spec does not apply to the object files that rgbasm outputs; their labels can include whatever weird characters.
Actually, RGBLINK in its entirety is not compliant: not only does it allow symbols beginning with illegal letters, it also emits illegal characters as-is instead of \u sequences.
Spec: https://rgbds.gbdev.io/sym/
Parser: https://docs.rs/gb-sym-file/latest/gb_sym_file/
!
is not allowed in symfiles according to the spec, but is used for anonymous labels. @ISSOtm suggested not outputting anything for anonymous labels.The text was updated successfully, but these errors were encountered: