GitHub user simonsouth opened a pull request:

    https://github.com/apache/thrift/pull/578

    THRIFT-2832: c_glib: Handle string lists correctly

    These commits
    
    - Add a unit test for C (GLib) that covers containers (initially only 
string lists, i.e. variables of type `list<string>`) used as
      - Parameters to a service method,
      - Return values from a service method and
      - Struct members with default values.
    - Fix the compiler so it correctly generates code in the above three cases.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/simonsouth/thrift 
thrift-2832-c_glib-handle-string-lists-correctly

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/thrift/pull/578.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #578
    
----
commit 5d1ad897c44a576adea62abadb9bb196cc6f1cc6
Author: Simon South <[email protected]>
Date:   2015-08-04T13:15:50Z

    c_glib: Library: Add unit test for containers
    
    This change adds a unit test that covers containers (initially
    only string lists) used as parameters to and return values from
    service methods, and as members with default values inside structs.

commit 11f8d3376b95447b46a7b0a0d49ca856a2cab226
Author: Simon South <[email protected]>
Date:   2015-08-04T13:22:57Z

    c_glib: Compiler: Handle string lists correctly
    
    With this change the compiler now correctly generates code for
    string lists (i.e. variables of type list<string>) that are
    
    - Passed as a parameter to a service method,
    - Returned from a service method or
    - Assigned a default value.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to