Yup, that's exactly what's happening. Now I wonder if it's safe to just #undef major and minor..
Thanks, Mike On Tuesday, September 30, 2014 2:03:01 PM UTC-4, Oliver wrote: > > I would guess that you are #including <sys/sysmacros.h> (perhaps > indirectly) which looks like this on my system: > > /* Access the functions with their traditional names. */ > #define major(dev) gnu_dev_major (dev) > #define minor(dev) gnu_dev_minor (dev) > #define makedev(maj, min) gnu_dev_makedev (maj, min) > > Oliver > > On 30 September 2014 16:11, Michael Sumulong <[email protected] > <javascript:>> wrote: > > I have a message where version information is passed and my message > fields > > contain a uint32's for major and minor numbers (as well as > > patch/pre_release/build info strings along the lines of semver.org). > When I > > use the version message type in my program, the major/minor fields show > up > > as gnu_dev_major/gnu_dev_minor. Is this normal behavior / documented > > anywhere? > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Protocol Buffers" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > To post to this group, send email to [email protected] > <javascript:>. > > Visit this group at http://groups.google.com/group/protobuf. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
