This has actually been a long-standing and very embarrassing problem. Embarrassing because SRCsd has handled this stuff for a long time. I thought I had filed this bug some time ago, but apparently not. Unlike #71, which is really scary, this is somewhat scary, though I think it can be done safely without too much trouble. It involves having the parser deal with calls that end in @0 or @m. I need to be really careful about this, because the parser is complex but seems to work correctly, and I want to keep it that way.
This has actually been a long-standing and very embarrassing problem. Embarrassing because SRCsd has handled this stuff for a long time. I thought I had filed this bug some time ago, but apparently not. Unlike #71, which is really scary, this is somewhat scary, though I think it can be done safely without too much trouble. It involves having the parser deal with calls that end in @0 or @m. I need to be really careful about this, because the parser is complex but seems to work correctly, and I want to keep it that way.