On 2014-12-03 02:38, Jim Brain wrote: > I think we need to decide on a set of assemblers that can handle things > like text and calculations and defines and such, and that becomes the > targets. If things like TASM or such cannot handle those constructs, we > ask the developers to consider adding them. IF I am right on this - that would have to go down to the 64 "native" level. > As for the other assemblers, I think a pretty simple AWK or PERL script > hosted on some web site (or Python, since that seems to be the language > of the week this week) Yeah - each language needs its five minutes. I don't understand what happened to this Python thing now too. > could be used to generate the respective source > for a specific assembler. If you need the dumbed down code, for any > project, feed it into this web page, and there you go. This is an interesting idea but since it doesn't look like a trivial task, I doubt anyone will do it anytime soon. Basically I understand this not as a simple search and replace kind of thing but rather quite a parser or parsers set that could parse each syntax correctly and "dumb the source down" as needed when output. That doesn't look like an afternoon type of project. Especially that things like KickAssembler is getting considerable momentum recently, which adds to the complexity. Sure - one doesn't need to Maybe I don't understand what you mean with "pretty simple [..] script" - I somehow don't see it anywhere close to pretty simple, even for the Python thing ;-) -- SD! Message was sent through the cbm-hackers mailing listReceived on 2014-12-03 09:00:03
Archive generated by hypermail 2.2.0.