1. 20 Sep, 2013 1 commit
  2. 18 Sep, 2013 1 commit
    • Max Cai's avatar
      Add two codegen parameters to nano. · 71766127
      Max Cai authored
      enum_style = c | java: 'c' to put the enum member int constants
      at the parent scope; 'java' to create uninstantiatable shell
      classes at the parent scope and put the int constants inside.
      
      optional_field_style = default | accessors: 'default' to create
      one public mutable field per optional proto field; 'accessors'
      to encapsulate the generated fields behind get, set, has and
      clear accessors.
      
      This CL only contains parsing code for these two parameters.
      
      Change-Id: Iec0c3b0f30af8eb7db328e790664306bc90be089
      71766127
  3. 08 Aug, 2013 2 commits
  4. 07 Aug, 2013 1 commit
  5. 05 Aug, 2013 1 commit
    • Max Cai's avatar
      Fix outer classname for javamicro/javanano. · 06eed37e
      Max Cai authored
      - File class name is defined as the java_outer_classname option value
        or the file name ToCamelCase; never the single message's ClassName.
      - File-scope enums are translated to constants in the file class,
        regardless of java_multiple_files.
      - If java_multiple_files=true, and file's class name equals a message's
        class name, no error. This is done by detecting that the outer class
        is not needed and skipping the outer class codegen and clash checks.
        Note: there is a disparity between java[lite] and the previous
        java{micr|nan}o: when generating code for a single-message proto, the
        outer class is omitted by java{micr|nan}o if the file does not have
        java_outer_classname. This change makes java{micr|nan}o align with
        java[lite] codegen and create the outer class, but will print some
        info to warn of potential change of code.
      - Also fixed the "is_own_file" detection and made all parseX() methods
        static. Previously, all messages in a java_multiple_files=true file
        are (incorrectly) considered to be in their own files, including
        nested messages, causing them to become inner classes (instance-
        bound) and forcing the parseX() methods to lose the static modifier.
      - This change supersedes c/60164 and c/60086, which causes javanano to
        put enum values into enum shell classes if java_multiple_files=true.
        We now always use the parent class to host the enum values. A future
        change will add a command line option to provide more flexibility.
      - Elaborated in java/README.txt.
      
      Change-Id: I684932f90e0a028ef37c662b221def5ffa202439
      06eed37e
  6. 31 Jul, 2013 2 commits
  7. 29 Jul, 2013 2 commits
  8. 26 Jul, 2013 2 commits
  9. 25 Jul, 2013 2 commits
    • Ulas Kirazci's avatar
      Add test for passing in proto params. · 2000cfdc
      Ulas Kirazci authored
      Depends on Ia532647fe8811d39230a23ba3671685b0388cbe0
      
      Change-Id: I0ba3ce3561aff31e246968a79b1d1053dec91d49
      2000cfdc
    • Max Cai's avatar
      Per-file java_multiple_files flag. · 4c4d6390
      Max Cai authored
      Imported source files may have different values for the 'java_multiple_files'
      option to the main source file's. Whether the fully qualified Java name of an
      entity should include the outer class name depends on the flag value in the
      file defining the referenced entity, not the main file. This CL loads the
      flag values from the main and all transitively imported files into the params,
      and generates the fully qualified Java names accordingly.
      
      If the generator option 'java_multiple_files' is set, its value overrides any
      in-file values in all source/imported files. This is because this generator
      option is typically used on either none or all source files.
      
      Change-Id: Id6a4a42426d68961dc669487d38f35530deb7d8e
      4c4d6390
  10. 23 Jul, 2013 3 commits
  11. 19 Jul, 2013 6 commits
  12. 09 Jul, 2013 5 commits
  13. 25 Jun, 2013 2 commits
  14. 24 Jun, 2013 1 commit
    • Brian Duff's avatar
      Nano support for extensions and unknown fields. · 5659cca8
      Brian Duff authored
      You can use the processor option store_unknown_fields to switch
      this support on:
      
        aprotoc --javanano_out=store_unknown_fields=true:/tmp/out
      
      A separate option for extensions isn't required. Support
      for unknown fields must be turned on to allow storing and
      retrieving extensions, because they are just stored as
      unknown fields. If unknown fields are switched on, extension
      related code will be generated when a proto message includes
      an extension range, or an extension is encountered.
      
      By default, store_unknown_fields is false. No additional
      code is generated, and the generator will error out if protos
      contain extension ranges or extensions.
      
      Change-Id: I1e034c9e8f3305612953f72438189a7da6ed2167
      5659cca8
  15. 07 Jun, 2013 3 commits
  16. 06 Jun, 2013 4 commits
  17. 05 Jun, 2013 1 commit
  18. 04 Jun, 2013 1 commit
    • Andrew Flynn's avatar
      Add toString() method to MessageNano. · a1612155
      Andrew Flynn authored
      - All of the real work for printing the proto is actually done in
        MessageNanoPrinter.
      - Uses reflection to find proto-defined fields and prints those.
      - Prints all fields, even defaults and nulls.
      - Also added a simple test to make sure it handles all proto types well.
        Tried not to make the test too brittle (but hey it's testing a toString()
        so how flexible can it be)
      
      Change-Id: I3e360ef8b0561041e010c1f3445ec45ecdcd2559
      a1612155