1. 14 Aug, 2019 1 commit
  2. 29 Jul, 2019 1 commit
    • Mark OLESEN's avatar
      ENH: support low-level reading of raw binary blocks (#1378) · bdc1c9bf
      Mark OLESEN authored
      - symmetric with writeRaw() etc for the output stream. These are
        methods that are not required by normal users, but which provide
        a finer granularity for reading.
      
      - additional information about the current stream position when
        endList fails. This may help when tracing errors.
      
      STYLE: change return type of beginRaw()/endRaw() to bool
      
      - was of type Ostream& for output, but return value was unused.
        Having bool may be better for encapsulating logic
      
      STYLE: remove unused Istream::readEndBegin() function
      bdc1c9bf
  3. 06 Feb, 2019 1 commit
  4. 01 Nov, 2018 1 commit
  5. 09 Nov, 2017 1 commit
  6. 05 Nov, 2017 1 commit
  7. 06 Nov, 2017 1 commit
  8. 23 Oct, 2017 1 commit
    • Mark OLESEN's avatar
      ENH: add reset() method to IStringStream · af5f8576
      Mark OLESEN authored
      - for convenience and symmetry with OStringStream
      
      STYLE: void return value for stream rewind() methods
      
      - this makes it easier to design bidirectional streams
      af5f8576
  9. 10 Nov, 2015 1 commit
  10. 01 Nov, 2015 1 commit
  11. 14 Aug, 2011 1 commit
  12. 19 Jan, 2011 1 commit
  13. 14 Jan, 2011 1 commit
  14. 07 Jan, 2011 1 commit
  15. 05 Jan, 2011 2 commits
  16. 28 Jul, 2010 1 commit
  17. 29 Mar, 2010 1 commit
  18. 15 Dec, 2009 1 commit
    • Mark Olesen's avatar
      Fix minor bug in ITstream · 3f0b6ec8
      Mark Olesen authored
      - The lineNumber of token::undefinedToken was being changed instead of
        just the lineNumber of the return token.
      
      - use List::first() and List::last() methods as well
      3f0b6ec8
  19. 03 Jan, 2009 1 commit
    • Mark Olesen's avatar
      reworked IOstreams · 1d866d7f
      Mark Olesen authored
      - Istream and Ostream now retain backslashes when reading/writing strings.
        The previous implementation simply discarded them, except when used to
        escape a double-quote or a newline. It is now vitally important to retain
        them, eg for quoting regular expression meta-characters.
      
        The backslash continues to be used as an escape character for double-quote
        and newline, but otherwise get passed through "as-is" without any other
        special meaning (ie, they are *NOT* C-style strings). This helps avoid
        'backslash hell'!
        For example,
           string:   "match real dots \.+, question mark \? or any char .*"
           C-style:  "match real dots \\.+, question mark \\? or any char .*"
      
      - combined subfiles in db/IOstreams, some had more copyright info than code
      - OPstreamI.H contained only private methods, moved into OPstream.C
      
      Are these really correct?
         IOstreams/Istream.H:#   include "HashTable.C"
         token/token.H:#define NoHashTableC
      1d866d7f
  20. 31 Dec, 2008 1 commit
  21. 25 Jun, 2008 2 commits
  22. 15 Apr, 2008 1 commit