The way I'd see it is you'd pass Core some option (--nocash-sym?) and it's generate a outputFile.sym mapping addresses to label names.
This could perhaps be achieved without special support from Core itself if NL!EA 11.1 -symOutput were to be supported here too (it would require an extra conversion step on the user's part but it would be feasible). However, because EA is already responsible for "automatically" mapping label values (file offsets) to addresses (which would be required for this feature), I feel like keeping this kind of computation within EA is the way to go.
Speaking of mapping file offsets to addresses, implementing something like this does conflict a bit with #6 (which tbh is a bit rubbish as it is), as it would consider every symbol as being a file offset which kind of defeats the purpose of being able to assign any value to a them. (I wish EA mapped labels automatically; It would have solved so many issues; but sadly changing that right now would probably break a lot of things... ).
The way I'd see it is you'd pass Core some option (
--nocash-sym
?) and it's generate aoutputFile.sym
mapping addresses to label names.This could perhaps be achieved without special support from Core itself if NL!EA 11.1
-symOutput
were to be supported here too (it would require an extra conversion step on the user's part but it would be feasible). However, because EA is already responsible for "automatically" mapping label values (file offsets) to addresses (which would be required for this feature), I feel like keeping this kind of computation within EA is the way to go.Speaking of mapping file offsets to addresses, implementing something like this does conflict a bit with #6 (which tbh is a bit rubbish as it is), as it would consider every symbol as being a file offset which kind of defeats the purpose of being able to assign any value to a them. (I wish EA mapped labels automatically; It would have solved so many issues; but sadly changing that right now would probably break a lot of things... ).
Let's assume this event file:
Invoking Core like this:
Would generate
Out.bin
as expected; and also aOut.sym
that looks like that:Here's doc on the no$ sym file format, for reference.