1. 11 Nov, 2015 1 commit
  2. 14 Aug, 2011 1 commit
  3. 19 Jan, 2011 1 commit
  4. 14 Jan, 2011 1 commit
  5. 07 Jan, 2011 1 commit
  6. 05 Jan, 2011 2 commits
  7. 28 Jul, 2010 1 commit
  8. 29 Mar, 2010 1 commit
  9. 11 Dec, 2009 2 commits
  10. 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
  11. 31 Dec, 2008 1 commit
  12. 25 Jun, 2008 2 commits
  13. 15 Apr, 2008 1 commit