On Wed, 2012-12-19 at 00:06 +0000, Peter Geoghegan wrote:
> On 18 December 2012 23:31, Josh Berkus <josh@agliodbs.com> wrote:
> > Jeff, Hackers:
> >
> > Is there a strong reason why this has to error?
>
> Having taken a look at the range I/O routines, I surmise that it was
> just easier to write range_parse() such that whitespace is included
> within <string> tokens:
There was some discussion about it, and the decision was made to match
record literal parsing for the sake of consistency. In a record literal,
spaces are considered to be a part of the value, so they are for range
types, as well.
Regards,
Jeff Davis