On Tue, Feb 14, 2012 at 1:50 PM, John J Barton
wrote:
> On Tue, Feb 14, 2012 at 10:45 AM, Rick Waldron
> wrote:
> >
> >
> > On Tue, Feb 14, 2012 at 1:51 AM, David Herman
> wrote:
> >>
> >> On Feb 13, 2012, at 4:03 PM, Rick Waldron wrote:
> >>
> >> > I speak for myself and my colleagues when I sa
On Tue, Feb 14, 2012 at 10:45 AM, Rick Waldron wrote:
>
>
> On Tue, Feb 14, 2012 at 1:51 AM, David Herman wrote:
>>
>> On Feb 13, 2012, at 4:03 PM, Rick Waldron wrote:
>>
>> > I speak for myself and my colleagues when I say that we've had our fill
>> > of including scripts _just_ for the sake of
On Tue, Feb 14, 2012 at 1:51 AM, David Herman wrote:
> On Feb 13, 2012, at 4:03 PM, Rick Waldron wrote:
>
> > I speak for myself and my colleagues when I say that we've had our fill
> of including scripts _just_ for the sake of having a common testing
> interface.
>
> A reasonable point. OTOH, I
There's both room and need for a built-in assert() IMHO -- I would like one
which magically compiles to nothing in production code.
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
On Feb 13, 2012, at 6:43 PM, Dean Landolt wrote:
> On a related note: has anyone given any thought to what shims should do about
> emulating @std modules? Or is there a programmatic loader API that's easy
> enough to shim in? That would make this kind of cowpath-paving far more
> fruitful.
The
On Feb 13, 2012, at 4:03 PM, Rick Waldron wrote:
> I speak for myself and my colleagues when I say that we've had our fill of
> including scripts _just_ for the sake of having a common testing interface.
A reasonable point. OTOH, I wouldn't want to over-engineer. And the larger the
API, the ha
On 2/13/12 at 16:03, waldron.r...@gmail.com (Rick Waldron) wrote:
Forget Date, typeof null, etc. JavaScript's biggest problem is devs that don't
test their code.
IMHO, things started going to the dogs in the mid-1970s when IBM
decided to "manage" bugs instead of fixing them. It't been
downh
On Mon, Feb 13, 2012 at 7:03 PM, Rick Waldron wrote:
>
>
> On Feb 13, 2012, at 2:21 PM, Domenic Denicola
> wrote:
>
> >> If you do a native Assertion module, maybe it should be similar to
> node's.
> >
> >> <http://nodejs.org/docs/latest/api/
On Feb 13, 2012, at 2:21 PM, Domenic Denicola
wrote:
>> If you do a native Assertion module, maybe it should be similar to node's.
>
>> <http://nodejs.org/docs/latest/api/assert.html>
>
> It's worth noting that Node's assert is almost (?) ident
> If you do a native Assertion module, maybe it should be similar to node's.
> <http://nodejs.org/docs/latest/api/assert.html>
It's worth noting that Node's assert is almost (?) identical to CommonJS's Unit
Testing spec [1]. I'm not sure which came first.
(I am sorry that I mistakenly sent this only to Rick Waldron. I
intended it for es-discuss.)
On Mon, Feb 13, 2012 at 5:04 PM, Rick Waldron wrote:
> I was wondering if a native Assertion module had ever been discussed or
> proposed - I searched[1] and found nothing. If anyone can point
wondering if a native Assertion module had ever been discussed
or proposed - I searched[1] and found nothing. If anyone can point me
to existing discussion or proposals that I might have missed, I was be
greatly appreciative. The simplest explanation of my thinking is
something closer to a "sta
I was wondering if a native Assertion module had ever been discussed or
proposed - I searched[1] and found nothing. If anyone can point me to
existing discussion or proposals that I might have missed, I was be greatly
appreciative. The simplest explanation of my thinking is something closer
to a
13 matches
Mail list logo