[
https://issues.apache.org/jira/browse/QPID-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996673#comment-12996673
]
Paul Colby commented on QPID-3027:
----------------------------------
The SWIG "Segfault on overloaded methods with different return types" issue I
reported has just been fixed :)
This means that we won't need to rename/ignore certain overloaded methods when
using SWIG 2.0.2+ (when its released; or r12471 in the meantime). So I think
the least confusing thing to do is %ignore the offending overloads on for
earlier versions of SWIG, rather than %rename them (which would introduce
entirely new function names - worth avoiding).
Type-mapping is 99% done... will upload soon! :)
> PHP binding of Qpid Messaging API
> ---------------------------------
>
> Key: QPID-3027
> URL: https://issues.apache.org/jira/browse/QPID-3027
> Project: Qpid
> Issue Type: New Feature
> Components: C++ Client
> Affects Versions: 0.8
> Reporter: Paul Colby
> Attachments: cqpid_php.diff
>
>
> Working on a PHP binding for the Qpid Messaging API via SWIG. There are
> several PHP-specific issues with C++ and SWIG which I've managed to
> workaround, so the binding is starting to take shape, but still very much a
> work in progress.
> The rough plan:
> 1. report relevant bugs / feature requests to SWIG (done).
> 2. clean-up Qpid php.i SWIG interface file (mostly done - just need to
> implement PHP namespaces).
> 3. implement qpid::types::Variant <-> PHP typemapping (not started).
> 4. implement printinfo pragma (should be easy, just need to choose what info
> to include).
> 5. create relevant [auto]makefile.
> Of course, there's lots of things to discuss / decide along the way... so
> I'll post 'em here as they come up.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
