1. 23 Feb, 1998 1 commit
  2. 01 Dec, 1997 1 commit
  3. 29 Jul, 1997 1 commit
  4. 03 Jun, 1997 1 commit
  5. 29 Apr, 1997 1 commit
  6. 27 Apr, 1997 2 commits
  7. 22 Apr, 1997 1 commit
    • Marc G. Fournier's avatar
      Major patch from Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov> · 9e2a87b6
      Marc G. Fournier authored
      OK, here are a passel of patches for the geometric data types.
      These add a "circle" data type, new operators and functions
      for the existing data types, and change the default formats
      for some of the existing types to make them consistant with
      each other. Current formatting conventions (e.g. compatible
      with v6.0 to allow dump/reload) are supported, but the new
      conventions should be an improvement and we can eventually
      drop the old conventions entirely.
      
      For example, there are two kinds of paths (connected line segments),
      open and closed, and the old format was
      
      '(1,2,1,2,3,4)' for a closed path with two points (1,2) and (3,4)
      '(0,2,1,2,3,4)' for an open path with two points (1,2) and (3,4)
      
      Pretty arcane, huh? The new format for paths is
      
      '((1,2),(3,4))' for a closed path with two points (1,2) and (3,4)
      '[(1,2),(3,4)]' for an open path with two points (1,2) and (3,4)
      
      For polygons, the old convention is
      
      '(0,4,2,0,4,3)' for a triangle with points at (0,0),(4,4), and (2,3)
      
      and the new convention is
      
      '((0,0),(4,4),(2,3))' for a triangle with points at (0,0),(4,4), and (2,3)
      
      Other data types which are also represented as lists of points
      (e.g. boxes, line segments, and polygons) have similar representations
      (they surround each point with parens).
      
      For v6.1, any format which can be interpreted as the old style format
      is decoded as such; we can remove that backwards compatibility but ugly
      convention for v7.0. This will allow dump/reloads from v6.0.
      
      These include some updates to the regression test files to change the test
      for creating a data type from "circle" to "widget" to keep the test from
      trashing the new builtin circle type.
      9e2a87b6
  8. 06 Apr, 1997 2 commits
  9. 05 Apr, 1997 2 commits
  10. 02 Mar, 1997 1 commit
  11. 01 Mar, 1997 1 commit
  12. 16 Jan, 1997 2 commits
  13. 14 Jan, 1997 1 commit
  14. 28 Dec, 1996 1 commit
  15. 13 Dec, 1996 1 commit
  16. 02 Dec, 1996 1 commit
  17. 18 Nov, 1996 1 commit
  18. 14 Nov, 1996 1 commit
  19. 30 Oct, 1996 1 commit
  20. 07 Oct, 1996 1 commit
  21. 06 Aug, 1996 1 commit
    • Marc G. Fournier's avatar
      Fixes: · ab57e09e
      Marc G. Fournier authored
      Also, I think that an extra source of noise in the diff of regress.out and
      expected.out is caused by not substituting the shared library file
      extension in the regression.input file (much like the paths and the
      usernames are sub'ed). This seems to be fixed with the following patches
      to regression.input and the Makefile... If I'm off base here, please tell!
      
      Submitted by:  Wayde Nie <niew@phoenix.cis.mcmaster.ca>
      ab57e09e
  22. 02 Aug, 1996 1 commit
  23. 01 Aug, 1996 1 commit
  24. 27 Jul, 1996 1 commit
  25. 25 Jul, 1996 1 commit
  26. 09 Jul, 1996 1 commit