[lucy-issues] [jira] [Commented] (CLOWNFISH-28) Proof-of-concept Go bindings

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on CLOWNFISH-28:
-----------------------------------------

GitHub user rectang opened a pull request:

    https://github.com/apache/lucy-clownfish/pull/13

    CLOWNFISH-28 proof-of-concept Go bindings v4

    Modify the proof-of-concept Go bindings to facilitate an implementation with better code generation.

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

    $ git pull https://github.com/rectang/lucy-clownfish CLOWNFISH-28-POC-Go-v4

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

    https://github.com/apache/lucy-clownfish/pull/13.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 #13
    
----
commit 6bacb27eb9f5f0cd0ac9aaa8c7cedc5336560c17
Author: Marvin Humphrey <ma...@rectangular.com>
Date:   2015-04-28T01:51:10Z

    Modify Go proof-of-concept design.
    
    *   Make structs public: `FooIMP` instead of `implFoo`.
    *   Embed parent structs.
    *   Make `ref` a `uintptr` instead of a pointer to a C type.
    *   Add the INITOBJ method to ObjIMP.
    *   Use one finalizer and call SetFinalizer from only one location.
    *   Implement TOPTR() only once.

----


> Proof-of-concept Go bindings
> ----------------------------
>
>                 Key: CLOWNFISH-28
>                 URL: https://issues.apache.org/jira/browse/CLOWNFISH-28
>             Project: Apache Lucy-Clownfish
>          Issue Type: New Feature
>            Reporter: Marvin Humphrey
>            Assignee: Marvin Humphrey
>             Fix For: 0.5.0
>
>
> Use mostly hand-rolled glue code for binding Go to limited portions of the Clownfish runtime.  A more extensible code-generation approach can follow later, but the early version helps to flesh out the design.



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