or relaxed
On May 12, 2008, at 8:10 AM, Peter Hall wrote:
Since both modes are to be specified by upcoming standards documents,
can we adopt some term other than standard for the mode we'd like
to
discourage? I propose loose.
I agree. But I think lenient sounds better.
Peter
What should ES4 do when there are too many or too few arguments?
Seems that the RI will apply different behavior depending on whether
the function arguments are typed or not. This is not necessarily
unexpected. I just want to nail down the rules as the RI and AS3
behave differently in this
There is a problem with that.
If it is an error to provide too many actual parameters to a function
with typed formal parameters, then you either must supply the correct
number of args or not type the args.
A use case that demonstrates the problem is the Array.some callback.
Usually it is
Of Michael O'Brien
Sent: 9. mai 2008 10:30
To: es4-discuss Discuss
Subject: Argument matching
What should ES4 do when there are too many or too few arguments?
Seems that the RI will apply different behavior depending on
whether the function arguments are typed or not. This is not
necessarily
an orthogonal concern.
I would expect excess arguments to typed functions to be ignored
silently,
as they can be picked up by 'arguments' inside the function.
--lars
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael O'Brien
Sent: 9. mai 2008 10:30
, 2008, at 12:00 PM, Lars Hansen wrote:
-Original Message-
From: Michael O'Brien [mailto:[EMAIL PROTECTED]
Sent: 9. mai 2008 11:49
To: Lars Hansen
Cc: es4-discuss Discuss
Subject: Re: Argument matching
Presumably what you're getting at is that if 'checker' is
strict then
it must
The RI (latest build) skips a finally block due to a break in catch:
for (i = 0; i 10; i++) {
print(i)
try {
throw throwing
}
catch (e) {
print(Catching)
break
}
finally {
, Michael O'Brien wrote:
Is the following valid?
var x = 2
var x = 3
The ES4 RI prevents this. ASC redefines x.
What should this do?
Michael
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
Thanks - a new build fixed it.
Michael
On May 1, 2008, at 4:14 PM, Graydon Hoare wrote:
Jeff Dyer wrote:
Works for me in the RI:
var x = 10; var x = 20; print(x)
20
As it should.
Could be an old build? Check one of the snapshots.
http://buildbot.ecmascript.org/es4/waterfall
I wanted to clarify the meaning of a static block. Consider:
class Shape {
static var count
var origin
static {
// Is this static initialization code?
count = 1
}
{
// Is this instance
I'm unsure how the class level initialization code should run:
Consider:
class Circle extends Shape {
print(Circle)
}
class Shape {
print(Shape)
}
The RI and ASC currently bomb on this due to the forward class
reference, however, my understanding is that this is perfectly legal.
Question about declarations:
Consider:
print(Shape.x)
public class Shape { public static var x = 1; }
print(Shape.x)
fun()
function fun() { print(fun); }
In the RI this prints:
undefined
1
fun
In ASC this prints:
1
1
fun
What happens in the RI is the class declaration seems to occur where
Jon, thanks. Any thoughts on the original post?
Question about declarations:
Consider:
print(Shape.x)
public class Shape { public static var x = 1; }
print(Shape.x)
fun()
function fun() { print(fun); }
In the RI this prints:
undefined
1
fun
In ASC this prints:
1
1
fun
and order of execution are different.
I prefer the current es4 behavior because static class initialization
code can predictably
use lexically scoped values. And it behaves like var declarations.
Michael O'Brien
On Apr 15, 2008, at 12:13 PM, Lars Hansen wrote:
-Original Message-
From
We define the slots for vars and functions first at the top of the block
and do initializations in-order where they reside in the code flow. So:
class XX {
function foo ...
// fooAlias exists here but is undefined
var fooAlias = foo
// fooAlias is now
, but it does strengthen the
integrity of what is ES4.
Michael O'Brien
~TMSteve
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
___
Es4-discuss mailing
This may be a little off topic for this group, so lets continue this
offline after this.
The ES4 spec is being written to not preclude off-device compilation.
After all, that is what AS3 does very well. So both approaches 1) all-
in-one compile/execution and 2) pre-compile then execute later
for server side processing.
What kind of server side were you interested in?
Michael O'Brien
Mbedthis Software
On Mar 8, 2008, at 3:14 PM, ToolmakerSteve98 wrote:
Are there any Open Source projects to develop server-side ECMAScript
4?
I'm in preliminary stages of locating (or starting if none
I'll vote for that also. It improves readability quite a bit.
But is there a better operator than "\"?
Shame "//" is taken. What about "/."
Michael
Lars Hansen wrote:
I have been pushing for this in
the past on several occasions, but enthusiasm in the WG has been scant,
What about the actual content sections?
We want the same look and feel over the text -- what perspectives do you
need covered in describing a feature. Do you have a sample?
Michael
Graydon Hoare wrote:
Brendan Eich wrote:
I'll start the ball rolling with writing up some notes on Program
Seems to me we may have some emerging agreement on the following items.
Please be kind if I'm overstating the consensus, but I believe the
following items start us in the right direction without being too
onerous.
Triage the existing proposals into those that are current and
correct and
Comments below:
This sounds good, but if we've accepted proposals and need detailed
specs, why not write specs? This is not just a matter of wiki
namespace (proposal: vs. spec:). Proposals have emphasized precedents,
use-cases, and anti-use-cases, and considered alternatives. Discussion
.
Michael
Graydon Hoare wrote:
Michael O'Brien wrote:
Could Graydon give a snapshot of what is not implemented in the RI in
terms of the proposals / features? I know the trac database lists
all, but a punch list of the high priority deficits would be helpful.
Sure. I can describe the state
Comments below:
Going further, I have mentally considered the language as providing 3
big categories of enhancement: fixtures, types, and namespaces. I
think that within -- and possibly between -- these groups there are
dependencies. For example, we can consider these levels of
the
language of multiple implementations. It needs further refinement, but
mostly it just needs to be done.
Your welcome. We are looking forward to releasing our first snapshot
soon.
Michael
Jd
On 2/15/08 11:20 PM, Michael O'Brien wrote:
Jeff,
Thanks for outlining the process to go
errors going forward.
thanks
Michael O'Brien
Mbedthis Software
Jeff Dyer wrote:
Hi,
We have entered a new phase in the development of the ES4 standard. Since
September we have had a fixed set of proposals to consider individually and
as a whole. The final step is to translate those
I'm trying to find the scope rules for constructor initializers and for
function parameter default values. If someone could point me to a
document or clarify these that would be great.
I've read bits and pieces. For constructor initializers:
class Shape {
function Shape():
leftSide
?
Thanks
Michael O'Brien
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
the use decimal pragma to use number NUMBER_TYPE. This
would allow for other number types. E.g.
use number decimal
use number int
2. We add support for int as the default number
3. We add long and ulong types that are by definition 64 bit. Also
support use number long
Michael O'Brien
- Original Message -
From: Michael O'Brien [EMAIL PROTECTED]
To: es4-discuss es4-discuss@mozilla.org
Sent: Thursday, December 13, 2007 7:10:41 PM (GMT-0500) America/New_York
Subject: Global functions
Are global functions declared with block or global scope. ie. declared
in the block
?
This is what many embedded devices need. I think the spec should
accommodate these devices without breaking the spec.
Michael
Lars T Hansen wrote:
On Dec 13, 2007 5:07 PM, Michael O'Brien [EMAIL PROTECTED] wrote:
I understand that the cut off for proposals is long past. But I
to predict and use.
Michael
Jeff Dyer wrote:
On 12/12/07 11:13 AM, Michael O'Brien wrote:
I've got a question about how user defined namespaces should resolve
inside of packages. This is really an ES4 implementation question and
not a usage question.
Consider:
package one {
public
Brendan,
I didn't see the reflect namespace documented in the overview.
Can you please provide some pointers to its doc?
Michael
Brendan Eich wrote:
On Nov 9, 2007, at 5:29 PM, Yuh-Ruey Chen wrote:
The confusion I'm getting is that there seems to be many ways to check
or
.
What's the Sesame Street song? "... one of these things is not
like the other, one of these things just doesn't belong."
You are not alone in wondering about these three -- this has
come up at past TG1 meetings and we went ahead and implemented to get
experience. Michael O
start with ES3 and selectively employ ES4
features as you wish.
Michael O'Brien
Steven Johnson wrote:
The suggestions of bloat and instability from some corners are rather
disingenuous when you consider that
(1) at least one high-quality ES4 engine (Tamarin) will be available with a
source
Doug,
Yes, I think the time has come to table the ES3+ materials.
It has been discussed on and off since April. Do you have something
that describes this proposal in a material way?
How can people evaluate ES4 vs ES3+ if ES3+ is unknown and unspecified?
Michael
Yehuda Katz wrote:
Doug,
many language features such as getter/setters by using
those facilities.
Lastly, as an implementer, having access to the technical materials:
grammar, wiki and most importantly the reference
implementation and test suite, has been invaluable and greatly
accelerated our efforts.
Michael O'Brien
qualified references as a namespace attribute.
I've posted the latest and greatest, dated 14-oct-2007.
Thanks,
Jd
On 10/14/07 11:25 AM, Michael O'Brien wrote:
This is probably for Jeff, but I'll send to the list anyway.
I was doing a scrub through the latest posted grammar and may h
38 matches
Mail list logo
