mungre

You can work around this by passing the `-w` flag to beebasm. This insists on a space between mnemonics and parameters so you can use macro names starting with mnemonics....

When using `-w`, rather than insisting on a space I think it would be sufficient just to add digits to the things it doesn't allow after a mnemonic (so alphas,...

I'd forgotten, macro names can end in $ or %. So you'd also have to add these to the list of things that can't go after a mnemonic when using...

I can't think of an example of a macro name that starts with a mnemonic and wouldn't cause problems, so I think that should just be "disallow macro names that...

The trouble with the minimum abbreviations listed in the user guide is that "useless" abbreviations are omitted. For example, "AS." resolves to ASC rather than ASN but this isn't documented....

This is in release v1.10 as the "-cycle" option.

FWIW, the current behaviour is consistent with BBC BASIC. +1 on checking calculated values. I'm wary of permitting negative immediate operands because a negative result might work well as 255...

Thank you, that looks good. (Discussed in #80)

I'm not sure about this one for v1.10. It is a good idea but it's also a breaking change potentially. @ZornsLemma what do you think?

I merged this into master manually since we're no longer using proposed-updates.