[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-c-dev
Subject:    [jira] [Closed] (AXISCPP-929) C interfaces should capture all C++ exceptions
From:       "nadir amra (Closed) (JIRA)" <axis-c-dev () ws ! apache ! org>
Date:       2012-01-20 5:29:39
Message-ID: 1704011599.59027.1327037379994.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/AXISCPP-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

nadir amra closed AXISCPP-929.
------------------------------

    
> C interfaces should capture all C++ exceptions
> ----------------------------------------------
> 
> Key: AXISCPP-929
> URL: https://issues.apache.org/jira/browse/AXISCPP-929
> Project: Axis-C++
> Issue Type: Bug
> Components: Client - API
> Reporter: nadir amra
> Assignee: nadir amra
> Fix For: current (nightly),  1.6 Final
> 
> 
> The C interfaces should catch all C++ exceptions and provide a way to indicate \
> whether operation was successful or not.  This means that we may have to eliminate \
> the dynamic generation of the C header files based on the C++ header files since \
> the prototypes for the calls may not be exactly the same - i.e. return value may \
> indicate success or failure and if the function returned some value, the value \
> returned on a the C interface may become an argument that would need to be passed \
> in.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: \
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more \
information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]