Updates:
Status: WontFix
Comment #16 on issue 247 by xiaof...@google.com: Ability to redirect file
output to stdout
https://code.google.com/p/protobuf/issues/detail?id=247
(No comment was entered for this change.)
--
You received this message because this project is configured to
Comment #13 on issue 247 by compuwar...@gmail.com: Ability to redirect file
output to stdout
http://code.google.com/p/protobuf/issues/detail?id=247
Discussion for implementing Java Parser moved to Issue 263
Comment #14 on issue 247 by compuwar...@gmail.com: Ability to redirect file
output to stdout
http://code.google.com/p/protobuf/issues/detail?id=247
Discussion for implementing Java Parser moved to Issue 263
--
You received this message because you are subscribed to the Google Groups
Comment #11 on issue 247 by compuwar...@gmail.com: Ability to redirect file
output to stdout
http://code.google.com/p/protobuf/issues/detail?id=247
Shall I create a new issue to track java parser so it can have it's own
fair discussion instead of being buried in this issue?
--
You
Comment #12 on issue 247 by ken...@google.com: Ability to redirect file
output to stdout
http://code.google.com/p/protobuf/issues/detail?id=247
Sure.
--
You received this message because you are subscribed to the Google Groups Protocol
Buffers group.
To post to this group, send email to
Comment #9 on issue 247 by compuwarescc: Ability to redirect file output to
stdout
http://code.google.com/p/protobuf/issues/detail?id=247
I've been thinking a lot of the use of run-time usage of .proto files in
java (I use this technique) and I've gone through two uses now - both
involve
Comment #8 on issue 247 by mike.wel...@gmail.com: Ability to redirect file
output to stdout
http://code.google.com/p/protobuf/issues/detail?id=247
You're also forgetting the C++/C world where each code generation will
output at least 2 files, a .cpp and a .h. So you would pretty much have
Comment #5 on issue 247 by compuwarescc: Ability to redirect file output to
stdout
http://code.google.com/p/protobuf/issues/detail?id=247
After further use, I think it's also (and possible more) important to
stream the output of the -o tag (a FileDescriptorProto buffer) to stdout.
If
Comment #6 on issue 247 by ken...@google.com: Ability to redirect file
output to stdout
http://code.google.com/p/protobuf/issues/detail?id=247
For -o, you can do:
protoc my.proto -o/dev/stdout
This just doesn't work with --java_out (or whatever lanugage) because it
would interpret
Comment #7 on issue 247 by compuwarescc: Ability to redirect file output to
stdout
http://code.google.com/p/protobuf/issues/detail?id=247
Seems to me that will only work on linux where /dev/stdout is a file
pointer to stdout.
Do you know of any way to do this on a windows platform?
--
Updates:
Status: Accepted
Labels: -Type-Defect Type-Enhancement
Comment #4 on issue 247 by ken...@google.com: Ability to redirect file
output to stdout
http://code.google.com/p/protobuf/issues/detail?id=247
We do already have the ability to output to a jar file. I suppose
Comment #2 on issue 247 by ken...@google.com: Ability to redirect file
output to stdout
http://code.google.com/p/protobuf/issues/detail?id=247
What happens if multiple files are generated? For example, if you
have option java_multiple_files = true; in your .proto file. This seems
like
Comment #1 on issue 247 by moofish32: Ability to redirect file output to
stdout
http://code.google.com/p/protobuf/issues/detail?id=247
I think this would be a very beneficial enhancement for the same reason.
Solves any concerns over permissions in the unix environment.
--
You received
13 matches
Mail list logo
