Re: Allow table.keyword rather than table['keyword']?

["Gary V. Vaughan" <gary@...>]

> On Mar 14, 2016, at 6:42 PM, Jonathan Goble <jcgoble3@gmail.com> wrote:
> 
> This is the main reason I support this change: because some keywords
> would otherwise be natural field names in a data table or object.
> "end" is one that I ran into while developing something for my
> matchext library, and instead of using "start" and "end" as fields for
> the start and end positions of a match, I ended up having to use
> "startpos" and "endpos". The ability to use "end" as a field name
> would be nice.

Forgive the grammar pedantry, but start & end do not go together anyway; you should use either 'begin' & 'end' or 'start' & 'finish'.

Cheers,
Gary