Skip to content
Snippets Groups Projects
  1. Nov 09, 2015
  2. Nov 07, 2015
    • dmh's avatar
      Fix github issues #140 · 5ad26bb6
      dmh authored
      1. Added check to libsrc4/nc4var.nc_def_var_extra to
         check that the no specified chunks size is greater than
         the dimension size.
      
      2. Added test to nc_test4/tst_chunks.c
      5ad26bb6
  3. Nov 06, 2015
  4. Nov 03, 2015
  5. Nov 02, 2015
  6. Oct 30, 2015
  7. Oct 29, 2015
  8. Oct 28, 2015
  9. Oct 27, 2015
  10. Oct 26, 2015
  11. Oct 24, 2015
  12. Oct 23, 2015
  13. Oct 22, 2015
  14. Oct 21, 2015
  15. Oct 20, 2015
    • Ward Fisher's avatar
      Merge pull request #136 from Unidata/issue134 · b672e4c5
      Ward Fisher authored
      Github issue 134:
      b672e4c5
    • dmh's avatar
      Github issue 134: · 370bd151
      dmh authored
      Their is an ambiguity in the DAP2 spec.  Section A.2 of the
      dap2 spec says:
        "...The backslash character (.\.) MAY be used as
         a single-character quoting mechanism only within
         quoted-string and comment constructs.
            quoted-pair = "\" CHAR
         ..."
      The underlying problem was to allow for " chars inside
      strings by using \". However, this definition is overbroad.
      It is not stated:
      1. if the backslash is to be left in the string or not.
      2. There is also an unstated, but related issue of what
         to do about e.g. '\n';convert to newline or not.
      
      This change is to conform to libdap and it does the following:
      1. The backslash is left in the string
      2. Things like \n are left as is and it is assumed that
         higher level code will decide what to do with e.g. \n.
      370bd151
Loading