Bug Tracker

Changes between Initial Version and Version 1 of Ticket #11010, comment 16


Ignore:
Timestamp:
04/26/12 09:07:34 (13 months ago)
Author:
jaubourg
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11010, comment 16

    initial v1  
    2222}}} 
    2323 
    24 while thanks to Exception not being caught and put in variables all the time, you code actually is: 
     24Which, by the way, is exactly what the Promise/A spec expects you to do in your fail callback. 
     25 
     26While thanks to Exception not being caught and put in variables all the time, you code actually is: 
    2527 
    2628{{{#!js 
    2729doSomething(); 
    2830}}} 
    29  
    30 Which, by the way, is exactly what the Promise/A spec expects you to do in your fail callback. 
    3131 
    3232> If there are insurmountable performance concerns about returning a new promise, though, then CommonJS/A compatability is indeed truly broken: