File: ChangeLog

package info (click to toggle)
yapps2 2.1.1-17
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 256 kB
  • ctags: 149
  • sloc: python: 1,008; makefile: 58; sh: 14
file content (108 lines) | stat: -rw-r--r-- 3,781 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
2003-08-27  Amit Patel  <amitp@cs.stanford.edu>

	* *: (VERSION) Release 2.1.1

	* *: Added a test/ directory for test cases; I had previously put
	tests in the examples/ directory, which is a bad place to put
	them.  Examples are useful for learning how Yapps works.  Tests
	are for testing specific features of Yapps.
	
	* parsetree.py (Plus.update): Fixed a long-standing bug in which
	the FOLLOW set of 'a'+ would include 'a'.  In theory this makes no
	practical difference because the 'a'+ rule eats up all the 'a'
	tokens anyway.  However, it makes error messages a little bit more
	confusing because they imply that an 'a' can follow.

	* yappsrt.py (print_error): Incorporated the context object into
	the printing of error messages.

2003-08-12  Amit Patel  <amitp@cs.stanford.edu>

	* *: (VERSION) Release 2.1.0
	
	* parsetree.py: Improved error message generation.  Instead of
	relying on the scanner to produce errors, the parser now checks
	things explicitly and produces errors directly.  The parser has
	better knowledge of the context, so its error messages are more
	precise and helpful.

	* yapps_grammar.g: Instead of setting self.rule in the setup()
	method, pass it in the constructor.  To make it available at
	construction time, pass it along as another attribute in the
	attribute grammar.

2003-08-11  Amit Patel  <amitp@cs.stanford.edu>

	* parsetree.py: Generated parsers now include a context object
	that describes the parse rule stack.  For example, while parsing
	rule A, called from rule B, called from rule D, the context object
	will let you reconstruct the path D > B > A.  [Thanks David Morley]
	
	* *: Removed all output when things are working
	properly; all warnings/errors now go to stderr.

	* yapps_grammar.g: Added support for A? meaning an optional A.
	This is equivalent to [A].

	* yapps2.py: Design - refactored yapps2.py into yapps2.py +
	grammar.py + parsetree.py.  grammar.py is automatically generated
	from grammar.g.  Added lots of docstrings.
	
2003-08-09  Amit Patel  <amitp@cs.stanford.edu>

	* yapps2.py: Documentation - added doctest tests to some of the
	set algorithms in class Generator.

	* yapps2.py: Style - removed "import *" everywhere.

	* yapps2.py: Style - moved to Python 2 -- string methods,
	list comprehensions, inline syntax for apply

2003-07-28  Amit Patel  <amitp@cs.stanford.edu>

	* *: (VERSION) Release 2.0.4
	
	* yappsrt.py: Style - replaced raising string exceptions
	with raising class exceptions.  [Thanks Alex Verstak]

	* yappsrt.py: (SyntaxError) Bug fix - SyntaxError.__init__ should
	call Exception.__init__

	* yapps2.py: Bug fix - identifiers in grammar rules that had
	digits in them were not accessible in the {{python code}} sections
	of the grammar.

	* yapps2.py: Style - changed "b >= a and b < c" to "a <= b < c"

	* yapps2.py: Style - change "`expr`" to "repr(expr)"

2002-08-00  Amit Patel  <amitp@cs.stanford.edu>

	* *: (VERSION) Release 2.0.3

	* yapps2.py: Bug fix - inline tokens using the r"" syntax weren't
	treated properly.

2002-04-00  Amit Patel  <amitp@cs.stanford.edu>

	* *: (VERSION) Release 2.0.2

	* yapps2.py: Bug fix - when generating the "else" clause, if the
	comment was too long, Yapps was not emitting a newline.  [Thanks
	Steven Engelhardt]	

2001-10-00  Amit Patel  <amitp@cs.stanford.edu>

	* *: (VERSION) Release 2.0.1

	* yappsrt.py: (SyntaxError) Style - the exception classes now
	inherit from Exception. [Thanks Rich Salz]

	* yappsrt.py: (Scanner) Performance - instead of passing the set
	of tokens into the scanner at initialization time, we build the
	list at compile time.  You can still override the default list per
	instance of the scanner, but in the common case, we don't have to
	rebuild the token list.  [Thanks Amaury Forgeot d'Arc]