trac problems
# Brendan Eich (17 years ago)
It's because ES1-3.1 use [[Class]], e.g., for internal property
names, and the "semantic brackets" are also trac wiki syntax.
One fix is to write trac plugins (Python scripts) to make these ECMA
[[Foo]] names format nicely. I'm nowhere near enough of a trac guru to
try this. Volunteers?
When I look at some trac tickets, I see a red box with an error message instead of expected text. For example, the first comment at < bugs.ecmascript.org/ticket/428>, cut-n-pasted into my email is:
Changed 1 monthbugs.ecmascript.org/timeline?from=2008-12-04T19%3A53%3A41Z%2B0000&precision=secondago
by brendan ¶ bugs.ecmascript.org/ticket/428#comment:1
At the Kona meeting, I thought we agreed to avoid making an array (say from another frame) indistinguishable according to isArray from an arguments object. At least the Array.prototype.concat method discriminates on Error: Failed to load processor Class
No macro or processor named 'Class' found
== "Array". We should provide the necessary minimal tools, at the least. Function.prototype.apply would want an isArrayLike predicate, but that should be named differently from isArray.
/be
A "View Selection Source" on the relevant part of the web page:
method discriminates on </p><div class="system-message"><strong>Error:
Failed to load processor <code>Class</code></strong><pre>No macro or
processor named 'Class' found</pre></div><p> == "Array".