Re: PATCH: safe numeric import

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Sep 29, 11:04am, Peter Stephenson wrote:
}
} OK, how about this?  When we're doing the import, all numbers, integer
} or floating point, are imported straight, without an evaluation.

This looks fine to me.  (I'm surprised that there never seems to have
been an IPDEF6 before.)

} Currently we suppress all errors from parameters at this stage, though
} we could make a special case and output errors when we truncate a
} numeric import because we ignored anything after an initial constant.

I could go either way on this one.  On the one hand it'd potentially
be nice to get a warning if someone is shoving a strange value through
SHLVL or something.  OTOH there's no reason to expect it to work so in
a non-malicious circumstance it shouldn't be necessary.