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

Robert Schweikert updated AXIS2C-1558:
--------------------------------------

    Attachment: axis2c_unusedVars.patch

The attached patch marks places where I was not sure about the appropriate 
action to take with comments, such as /*Ooops....*/, /*Something probably 
wrong*/, and /*Ignore...*/
(sorry about the inconsistency).

In other places where I was reasonably confident about what to do I implemented 
what I thought would be the appropriate action.

There are a couple of places where I replaced the use of "read" with "write" in 
a check.

There are also a number of places where I commented out the offending variables 
as I thought they were superfluous.

Someone who knows the spec and the code base should be able to use this as a 
starting point. At the very least this patch identifies all places where the 
compiler complains.

> axis2c does not build with gcc4.6 and warnings turned into errors
> -----------------------------------------------------------------
>
>                 Key: AXIS2C-1558
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1558
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>         Environment: openSUSE build service factory build
>            Reporter: Robert Schweikert
>              Labels: build
>         Attachments: axis2c_unusedVars.patch
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> THe current release 1.6.0 of the code base does not build when compiled with 
> gcc 4.6 and warnings turned into errors. The problem is a relatively large 
> number of unused/unchecked returm values in the code base.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to