On Tue, Aug 6, 2013 at 1:02 PM, Allen Wirfs-Brock wrote:
> Has anybody ever actually seen a JS exception handler that really needs to
> take conditional action depending upon whether as TypeError or RangeError
> was thrown?
>
For what it's worth, as someone using both promises and custom error ty
s just
> not obvious to me what authors are expected to do if they want to
> throw a machine readable error. I.e. one that allows code to catch the
> error and handle it.
>
> / Jonas
> ___
> es-discuss mailing list
> es-discuss@m
On Wed, Jun 19, 2013 at 7:01 AM, Mark S. Miller wrote:
> On Wed, Jun 19, 2013 at 3:28 AM, Alex Russell wrote:
>
>>
>> What was less clear is that there's any real problem with error handling:
>> polyfills can (should?) keep lists of unhandled promises and make them
>> available to tools while we
; force an error being thrown and, if uncaught, it generates a stack trace
>> leaking the line number even without the API you're asking for (but that
>> would work only once)
>>
>>
>> I see this as being similar to asking for a portable
4 matches
Mail list logo