Thank you very much Dave for your quick and detailed replies
I'll try that out soon.
Aviad
On 1 דצמבר, 04:50, daveb <[EMAIL PROTECTED]> wrote:
> BTW: I just released protobuf-c 0.6 which include the item__init()
> function (and it also supports default-values properly now).
>
> - dave
>
> On Nov
BTW: I just released protobuf-c 0.6 which include the item__init()
function (and it also supports default-values properly now).
- dave
On Nov 27, 7:48 pm, daveb <[EMAIL PROTECTED]> wrote:
> I should mention too: I plan to eventually add a generated function
> "item__init(Item *)" to initialize
I should mention too: I plan to eventually add a generated function
"item__init(Item *)" to initialize a message. i plan to add this when
i fix default values for non-fundamental types (which are currently
ignored).
(i haven't had a huge amount of time to deal with these few niggling
issues, bu
The reason why it is crashing is that all messages have a few builtin
members that are usually initialized via ITEM__INIT. If you look at
the generated Item it looks like:
struct _Item
{
ProtobufCMessage base_message;
uint32_t id;
};
The best way to construct a message is to use C
cc'ing Dave Benson, who maintains the only C port I'm aware of.
On Tue, Nov 25, 2008 at 8:54 AM, <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I'm using the protocol buffers package for c. It's very useful and
> handy. However I've encountered a problem when trying to use a message
> with a nested repea
Hi,
I'm using the protocol buffers package for c. It's very useful and
handy. However I've encountered a problem when trying to use a message
with a nested repeated field of an other message type.
This is the simplified version -
message Item {
int32 id = 1;
}
message LookupReply {
