<!-- 
RSS generated by JIRA (4.4#649-r158309) at Wed Jun 19 23:34:08 CDT 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://dev.clojure.org/jira/si/jira.issueviews:issue-xml/CLJS-429/CLJS-429.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Clojure JIRA</title>
    <link>http://dev.clojure.org/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>4.4</version>
        <build-number>649</build-number>
        <build-date>25-07-2011</build-date>
    </build-info>

<item>
            <title>[CLJS-429] Data Conveying Exception: ex-data and ex-info</title>
                <link>http://dev.clojure.org/jira/browse/CLJS-429</link>
                <project id="10040" key="CLJS">ClojureScript</project>
                        <description>&lt;p&gt;equivalent of &lt;a href=&quot;http://dev.clojure.org/jira/browse/CLJ-733&quot;&gt;http://dev.clojure.org/jira/browse/CLJ-733&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;as per &lt;a href=&quot;https://groups.google.com/d/topic/clojure/vlTR_161WNc/discussion&quot;&gt;https://groups.google.com/d/topic/clojure/vlTR_161WNc/discussion&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;see also:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/clojure/clojure/blob/d0c380d9809fd242bec688c7134e900f0bbedcac/src/clj/clojure/core.clj#L4227&quot;&gt;https://github.com/clojure/clojure/blob/d0c380d9809fd242bec688c7134e900f0bbedcac/src/clj/clojure/core.clj#L4227&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://dev.clojure.org/display/design/Error+Handling&quot;&gt;http://dev.clojure.org/display/design/Error+Handling&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="15859">CLJS-429</key>
            <summary>Data Conveying Exception: ex-data and ex-info</summary>
                <type id="4" iconUrl="http://dev.clojure.org/jira/images/icons/improvement.gif">Enhancement</type>
                                <priority id="4" iconUrl="http://dev.clojure.org/jira/images/icons/priority_minor.gif">Minor</priority>
                    <status id="5" iconUrl="http://dev.clojure.org/jira/images/icons/status_resolved.gif">Resolved</status>
                    <resolution id="1">Completed</resolution>
                                <assignee username="michalmarczyk">Micha&#322; Marczyk</assignee>
                                <reporter username="davesann">Dave Sann</reporter>
                        <labels>
                    </labels>
                <created>Mon, 26 Nov 2012 05:24:41 -0600</created>
                <updated>Thu, 6 Dec 2012 10:18:43 -0600</updated>
                    <resolved>Thu, 6 Dec 2012 10:18:43 -0600</resolved>
                                                                    <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="30174" author="michalmarczyk" created="Wed, 5 Dec 2012 17:47:56 -0600"  >&lt;p&gt;The attached patch introduces ex-info, ex-data and ExceptionInfo to cljs.core. ExceptionInfo has its prototype set to Error.prototype (apparently necessary for good behaviour across browsers; this is marked as a special case in a comment).&lt;/p&gt;

&lt;p&gt;The version of ex-info introduced by the patch does support a cause argument, but I have to say that it&apos;s not clear to me how user code should go about extracting it. Direct property access feels icky; a new fn would be possible, but should perhaps be shared with Clojure; Clojure code would say (.getCause ex), but hanging a method on ExceptionInfo somehow feels icky to me too. My first cut at the patch actually did not include the cause field in ExceptionInfo and the ternary variant of ex-info; that could actually be a reasonable approach for now, especially if introducing a new fn might be a possibility (since that would presumably require coordination with Clojure).&lt;/p&gt;</comment>
                    <comment id="30176" author="michalmarczyk" created="Thu, 6 Dec 2012 06:17:35 -0600"  >&lt;p&gt;An improved patch. Firstly, it correctly makes ExceptionInfo into a custom error type (the original patch was broken on this point). Secondly, it introduces ex-message and ex-cause for dealing with ExceptionInfo in a platform-agnostic manner (got the go-ahead from Rich @ ClojureX; I&apos;ll be submitting a patch for this to Clojure).&lt;/p&gt;</comment>
                    <comment id="30178" author="michalmarczyk" created="Thu, 6 Dec 2012 06:23:50 -0600"  >&lt;p&gt;Clojure patch @ &lt;a href=&quot;http://dev.clojure.org/jira/browse/CLJ-1120&quot; title=&quot;Introduce ex-message and ex-cause to abstract away the platform in dealing with ExceptionInfo&quot;&gt;CLJ-1120&lt;/a&gt;.&lt;/p&gt;</comment>
                    <comment id="30180" author="dnolen" created="Thu, 6 Dec 2012 10:18:43 -0600"  >&lt;p&gt;fixed, &lt;a href=&quot;http://github.com/clojure/clojurescript/commit/7ccb67e040d32b2c0112d2c73dd2e28d5e13c50a&quot;&gt;http://github.com/clojure/clojurescript/commit/7ccb67e040d32b2c0112d2c73dd2e28d5e13c50a&lt;/a&gt;&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                    <attachment id="11748" name="0001-CLJS-429-Data-Conveying-Exception-ex-data-and-ex-inf.patch" size="2812" author="michalmarczyk" created="Thu, 6 Dec 2012 06:17:35 -0600" />
                </attachments>
            <subtasks>
        </subtasks>
                <customfields>
                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-global-rank">
                <customfieldname>Global Rank</customfieldname>
                <customfieldvalues>
                    
                </customfieldvalues>
            </customfield>
                                                                                                            </customfields>
    </item>
</channel>
</rss>