Hrvoje Niksic <hniksic(a)srce.hr> writes:
When I created the `string' function, I made it accept integers
(via
CHECK_CHAR_COERCE_INT) out of inertia.
Today it crossed my mind that `string' is a new function and
there is
no compatibility code actually depending on it accepting integers.
Should we make new functions behave logically, i.e. accept only
characters where characters are expected? I lean toward this.
I would say no.
Another question: do we care about FSF compatibility? FSF also has
`string', and they certainly accept integers.
We care where it otherwise hurts. If it's going to accept integers
the DOC string needs to be corrected.