You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2016/02/11 11:10:18 UTC

[jira] [Commented] (PROTON-1094) c++: refactor and documentation of type conversions

    [ https://issues.apache.org/jira/browse/PROTON-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142506#comment-15142506 ] 

Robbie Gemmell commented on PROTON-1094:
----------------------------------------

[~aconway] what is the status on this? Done? Bump to 0.13.0? Other?

> c++:  refactor and documentation of type conversions
> ----------------------------------------------------
>
>                 Key: PROTON-1094
>                 URL: https://issues.apache.org/jira/browse/PROTON-1094
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: cpp-binding
>    Affects Versions: 0.11.1
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.12.0
>
>
> Original design was to use stream operator << >> interface to proton::data to give complete flexibility to construct/interpret arbitrary AMQP types in a usable, idiomatic C++ way.
> This interface is important internally but most API users will use automatic conversion via assignment, construction and get<T>() functions on proton::value and the proton::scalar types. 
> Move detailed documentation for the type conversion rules to proton::value, and mark the data interface as "advanced" but leave it available to cover possible interop cases that are not covered by the existing "canned" conversions.
> Review proton::message constructors, assignment and documentation to make sure it is easy to understand how to use data-containing members of a message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)