[
http://issues.apache.org/jira/browse/AXISCPP-808?page=comments#action_12319810
]
Henrik Nordberg commented on AXISCPP-808:
-
I suggest using std::auto_ptr instead of using operator delete directly.
Include .
Also, this code looks strange:
[
http://issues.apache.org/jira/browse/AXISCPP-808?page=comments#action_12319820
]
Samisa Abeysinghe commented on AXISCPP-808:
---
stringstream seem to be a good suggestion. However, how portable this would be
across platforms?
Regarding replacing
[
http://issues.apache.org/jira/browse/AXISCPP-808?page=comments#action_12319831
]
Denis Linine commented on AXISCPP-808:
--
If decided to optimize the code throwing the exceptions, one could write it
like this:
AxisChar msg[256];
sprintf(length,
[
http://issues.apache.org/jira/browse/AXISCPP-808?page=comments#action_12319832
]
Denis Linine commented on AXISCPP-808:
--
Sorry, should be
If decided to optimize the code throwing the exceptions, one could write it
like this:
AxisChar msg[256];
s
[
http://issues.apache.org/jira/browse/AXISCPP-808?page=comments#action_12319840
]
Denis Linine commented on AXISCPP-808:
--
AxisChar* serializedValue = new char[80];
AxisSprintf (serializedValue, 80, "%f", *value);
IAnySimpleType::serialize(serialized
[
http://issues.apache.org/jira/browse/AXISCPP-808?page=comments#action_12319844
]
Denis Linine commented on AXISCPP-808:
--
I think that one could even change the code so that getMaxInclusive() and
similar functions would return objects by value. Retur
[
http://issues.apache.org/jira/browse/AXISCPP-808?page=comments#action_12320246
]
Samisa Abeysinghe commented on AXISCPP-808:
---
If I remember correct, the rationale to have the pointers as return values was
something related to nillable values. H
