Issue 48: v8 code is not const-correct.
http://code.google.com/p/v8/issues/detail?id=48
Comment #4 by [EMAIL PROTECTED]:
Duplicate of issue 38.
Issue attribute updates:
Status: Duplicate
--
You received this message because you are listed in the owner
or CC fields of this issue, or be
Issue 48: v8 code is not const-correct.
http://code.google.com/p/v8/issues/detail?id=48
Comment #3 by i3x171um:
That would be quite a significant change to the public API of V8. As a
third party
user, I would much prefer this change be made sooner rather than later, if
it is to
be made at all
Issue 48: v8 code is not const-correct.
http://code.google.com/p/v8/issues/detail?id=48
Comment #2 by pete.gontier:
While 48 may be a duplicate of 38, 48 contains valuable explanation and
references which 38 should have
included.
--
You received this message because you are listed in the ow
Issue 48: v8 code is not const-correct.
http://code.google.com/p/v8/issues/detail?id=48
Comment #1 by [EMAIL PROTECTED]:
Sorry. Just saw that this is actually a duplicate of Issue 38.
http://code.google.com/p/v8/issues/detail?id=38&colspec=ID%20Type%20Status%20Priority%20Owner%20Summary
--
Yo
Issue 48: v8 code is not const-correct.
http://code.google.com/p/v8/issues/detail?id=48
New issue report by [EMAIL PROTECTED]:
The v8 Code ist not const-correct. At least the API should provide
const-correct behaviour or else it is hard to use it with any good C++ code.
e.g.
virtual int ScriptD
