search

mhowlett / NNanomsg

.NET binding for nanomsg
MIT License
179 stars 52 forks source link

SendImediate produces Assertion Error Unused Symbol #17

Open ghost opened 10 years ago

ghost commented 10 years ago

calling SendImediate produces AssertionError:

        Unused symbol

        NN_NS_VERSION,
        NN_NS_DOMAIN,
        NN_NS_TRANSPORT,
        NN_NS_PROTOCOL,
        NN_NS_OPTION_LEVEL,
        NN_NS_SOCKET_OPTION,
        NN_SOCKET_NAME,
        NN_NS_TRANSPORT_OPTION,
        NN_NS_OPTION_TYPE,
        NN_NS_OPTION_UNIT,
        NN_NS_FLAG,
        NN_NS_ERROR,
        NN_NS_LIMIT,
        NN_TYPE_NONE,
        NN_TYPE_INT,
        NN_TYPE_STR,
        NN_UNIT_NONE,
        NN_UNIT_BYTES,
        NN_UNIT_MILLISECONDS,
        NN_UNIT_PRIORITY,
        NN_UNIT_BOOLEAN,
        NN_UNIT_SOCKET_NAME

adding the variables to NanomesgSymbols.cs will remove the Assert-Error. But it would make send to also initialize them in Enums.cs

kwpatrick commented 10 years ago

I'm adding these. The main new feature is the socket name socketopt, working on that one as well. The socket name isn't roundtripping with our current interop methods, so I'm investigating.

On Mon, Jul 7, 2014 at 3:59 AM, Eddy notifications@github.com wrote:

calling SendImediate produces AssertionError:

    Unused symbol

    NN_NS_VERSION,
    NN_NS_DOMAIN,
    NN_NS_TRANSPORT,
    NN_NS_PROTOCOL,
    NN_NS_OPTION_LEVEL,
    NN_NS_SOCKET_OPTION,
    NN_SOCKET_NAME,
    NN_NS_TRANSPORT_OPTION,
    NN_NS_OPTION_TYPE,
    NN_NS_OPTION_UNIT,
    NN_NS_FLAG,
    NN_NS_ERROR,
    NN_NS_LIMIT,
    NN_TYPE_NONE,
    NN_TYPE_INT,
    NN_TYPE_STR,
    NN_UNIT_NONE,
    NN_UNIT_BYTES,
    NN_UNIT_MILLISECONDS,
    NN_UNIT_PRIORITY,
    NN_UNIT_BOOLEAN,
    NN_UNIT_SOCKET_NAME

adding the variables to NanomesgSymbols.cs will remove the Assert-Error. But it would make send to also initialize them in Enums.cs

— Reply to this email directly or view it on GitHub https://github.com/mhowlett/NNanomsg/issues/17.