On 13 July 2013 22:10, Dmitry Gutov <dgutov@yandex.ru> wrote:
On 13.07.2013 14:23, Bozhidar Batsov wrote:Sure, it's now easier to do correctly. Done. :)
Great! Btw, shouldn't we highlight the conversion methods from Kernel
(Float, Integer, etc) as built-ins?
Thanks!But we have to highlight these abbreviation-named modules *somehow*. And we're bound to be wrong in 50% of these cases. That's why I don't think it's a good idea.
But there's really nothing that would distinguish a Math::E
reference from Foo::C. Or from GC, IO, DL, IRB, URI, XML, HTML, etc.
Yep, I'm aware we can't distinguish all cases without the use of a
proper parser, but I guess we should handle accordingly at least the
scenarios which are deterministic.
That difference in highlighting wouldn't convey much information anyway: uppercase text with underscores is easy to notice as it is.Fair enough :-)