P
Pavils Jurjans
Hallo,
I yesterday was browsing the book, JavaScript The Definitive Guide
(4th ed), which is, unquestionably, the best reference book for JS. To
my surprise, I didn't find any documentation about the static
properties of global RegExp object, ie, RegExp.lastMatch,
RegExp.leftContext, RegExp.rightContext, and all those RegExp.$x
properties. I lloked up the ECMA-262 PDF and to my surprise realized
that they are not included into the standard.
I don't wuite know the reasons, why it is done so, I may guess that
it's because of their awkward namespace. Still, that functionality is
specified in core JavaScript 1.2 (at least JavaScript the Definitive
Guide 3rd ed states so), and I doubt that such features would be taken
off from the JavaScript standard in future. It's somewhat bitter that
the 4th edition focuses on ECMA standard rather than JavaScript.
But now, I am quite concerned about the future of those RegExp object
properties. I there some info about their possible inclusion in the
ECMA standard? Is it now 'deprecated' to use them, and coders should
use workarounds?
Thanks,
-- Pavils
I yesterday was browsing the book, JavaScript The Definitive Guide
(4th ed), which is, unquestionably, the best reference book for JS. To
my surprise, I didn't find any documentation about the static
properties of global RegExp object, ie, RegExp.lastMatch,
RegExp.leftContext, RegExp.rightContext, and all those RegExp.$x
properties. I lloked up the ECMA-262 PDF and to my surprise realized
that they are not included into the standard.
I don't wuite know the reasons, why it is done so, I may guess that
it's because of their awkward namespace. Still, that functionality is
specified in core JavaScript 1.2 (at least JavaScript the Definitive
Guide 3rd ed states so), and I doubt that such features would be taken
off from the JavaScript standard in future. It's somewhat bitter that
the 4th edition focuses on ECMA standard rather than JavaScript.
But now, I am quite concerned about the future of those RegExp object
properties. I there some info about their possible inclusion in the
ECMA standard? Is it now 'deprecated' to use them, and coders should
use workarounds?
Thanks,
-- Pavils