That's not strange. That's a Windows feature :-)
On 5 Aug., 01:50, Kenton Varda wrote:
> Yes, that's correct. If the Win32 API strips trailing whitespace from file
> names when opening them, that would explain why there was no error -- but
> that's very strange behavior IMO.
>
> On Tue, Aug 4,
Yes, that's correct. If the Win32 API strips trailing whitespace from file
names when opening them, that would explain why there was no error -- but
that's very strange behavior IMO.
On Tue, Aug 4, 2009 at 4:26 PM, Tai wrote:
>
> This could be a windows problem where white spaces are accepted w
This could be a windows problem where white spaces are accepted when
doing a file lookup. I further assume when protoc takes the argument
it uses the filename including the white space to generate the class
name. Maybe that was the reason why the class was called
"MyClassProto" and not "MyClass".
In that case I'm surprised it compiled -- I would have expected protoc to
report "file not found". Weird.
On Tue, Aug 4, 2009 at 2:16 PM, Tai wrote:
>
> Thanks. Your were pointing into the right direction. It wasn't the
> filename but the compile argument when using ant:
>
> basedir="../../../
Thanks. Your were pointing into the right direction. It wasn't the
filename but the compile argument when using ant:
The argument was:
value="
It looks like your problem is that your file name actually has a space
tacked on to the end of it. That is, the name is "MyClass.proto " <- note
the last space. You should get rid of that space.
On Tue, Aug 4, 2009 at 9:54 AM, Tai wrote:
>
> I got a strange behaviour when compiling a protofile
What it is also funny is that my file ADMObjectHandleMessage.proto
looks like this:
package com.qnamic.base.agent;
option java_outer_classname = "ADMObjectHandleMessage";
message ADMObjectHandle {
optional string host = 1;
optional string agent = 2;
optional string path = 3;
optio
Yes, I am using Windows XP and Eclipse 3.5
On 4 Aug., 19:49, Stefan wrote:
> Are you using Windows by any chance?
>
> On Aug 4, 11:54 am, Tai wrote:
>
> > I got a strange behaviour when compiling a protofile (e.g.
> > MyClass.proto). The generated java class is then called MyClassProto.
> > All
Are you using Windows by any chance?
On Aug 4, 11:54 am, Tai wrote:
> I got a strange behaviour when compiling a protofile (e.g.
> MyClass.proto). The generated java class is then called MyClassProto.
> All other proto files works fine. As a workaround I have added the
> following line to the pr
I got a strange behaviour when compiling a protofile (e.g.
MyClass.proto). The generated java class is then called MyClassProto.
All other proto files works fine. As a workaround I have added the
following line to the proto file:
option java_outer_classname = "MyClass";
Any idea what I am doing
10 matches
Mail list logo
