W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2013

[Bug 23532] Dealing with undefined

From: <bugzilla@jessica.w3.org>
Date: Thu, 24 Oct 2013 22:08:33 +0000
To: public-script-coord@w3.org
Message-ID: <bug-23532-3890-UbUVp5UGy6@http.www.w3.org/Bugs/Public/>

--- Comment #35 from Glenn Maynard <glenn@zewt.org> ---
(In reply to Rick Waldron from comment #34)
> (In reply to Glenn Maynard from comment #33)
> > Verifying the number of parameters is not "excess validation".  Verifying
> > the number of parameters is a useful and well-understood part of modern
> > dynamic languages.  See Python for a good example.
> If a specific number of arguments is necessary for the given function to
> maintain its invariants, then the function should be defined with named
> formal parameters.

I can't tell what your reply has to do with what I wrote.  Named formal
parameters are what we're discussing.  Please clarify.

> > We can't get this everywhere in JavaScript due to heavy legacy constraints,
> > but that doesn't mean we shouldn't have it at all.
> There are no constraints described in your response.

There weren't intended to be.  Everybody reading this thread already knows that
web compatibility is the legacy that constrains changing web APIs.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 24 October 2013 22:08:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:18 UTC