dev-lang/stratego/ChangeLog


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

# ChangeLog for dev-lang/stratego
# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL
# $Header: /var/cvsroot/gentoo-x86/dev-lang/stratego/ChangeLog,v 1.8 2003/01/09 22:10:01 karltk Exp $

  09 Jan 2003; Karl Trygve Kalleberg <karltk@gentoo.org> stratego-0.8.1.ebuild:
  Added a fix by styx to make it compile properly.

  09 Jan 2003; Karl Trygve Kalleberg <karltk@gentoo.org> : masked 0.8 for
  testing again. It has a minor bug in its build system that needs to fixed.

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
*stratego-0.8.1 (20 Oct 2002)

  20 Oct 2002; Karl Trygve Kalleberg <karltk@gentoo.org> stratego-0.8.1.ebuild files/digest-stratego-0.8.1 :
  New upstream version.

  02 Nov 2002; Karl Trygve Kalleberg <karltk@gentoo.org> stratego-0.8.1.ebuild :
  Fixed sandbox violation. 

*stratego-0.8 (20 Oct 2002)

  02 Nov 2002; Karl Trygve Kalleberg <karltk@gentoo.org> stratego-0.8.ebuild :
  Fixed sandbox violation. 

  20 Oct 2002; Karl Trygve Kalleberg <karltk@gentoo.org> stratego-0.8.ebuild files/digest-stratego-0.8 :
  New upstream version.

*stratego-0.7 (11 Apr 2002)

  02 Nov 2002; Karl Trygve Kalleberg <karltk@gentoo.org> stratego-0.7.ebuild files/digest-stratego-0.7 :
  This version violates the sandbox and is superceded by 0.8, so I'm removing 
  it.

  11 Apr 2002; Karl Trygve Kalleberg <karltk@gentoo.org> stratego-0.7.ebuild files/digest-stratego-0.7:

  Stratego is a modular language for the specification of fully automatic 
  program transformation systems based on the paradigm of RewritingStrategies.

  In Stratego, basic transformation rules are expressed by means of labeled 
  conditional rewrite rules. Exhaustively applying all rewrite rules in a 
  collection of valid rules is often not desirable; a system of rules can be 
  non-terminating, or, more frequently, non-confluent. The latter means that 
  different outcomes of the normalization process are possible depending on 
  the position of application and the selection of rules. Therefore, it is
  necessary to have more control over the application of rules. In standard 
  systems based on rewriting, normalization is controlled by a fixed default 
  RewritingStrategy. In such systems more control is achieved by encoding the 
  desired strategy with additional rewrite rules that spell out a traversal 
  over the abstract syntax tree and apply the transformations in the desired 
  order.