diff options
| author | aarne <aarne@cs.chalmers.se> | 2007-12-17 18:12:46 +0000 |
|---|---|---|
| committer | aarne <aarne@cs.chalmers.se> | 2007-12-17 18:12:46 +0000 |
| commit | 27602f4f8291f4d6a8b4b7109caf321d16cb6c99 (patch) | |
| tree | 8e64b75d15c3b9f80c543466ad37aa5536a86f8c /src/GF/GFCC/doc/gfcc.txt | |
| parent | 7551c70db6c76a796e93fa1cd4ebe7c850344b7e (diff) | |
took back smart type of Int ; Digits type in resource and some adjustments of Det syntax (not yet for romance and russian)
Diffstat (limited to 'src/GF/GFCC/doc/gfcc.txt')
| -rw-r--r-- | src/GF/GFCC/doc/gfcc.txt | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/src/GF/GFCC/doc/gfcc.txt b/src/GF/GFCC/doc/gfcc.txt index 6a78a62f6..5dcf2fbdc 100644 --- a/src/GF/GFCC/doc/gfcc.txt +++ b/src/GF/GFCC/doc/gfcc.txt @@ -1,6 +1,6 @@ The GFCC Grammar Format Aarne Ranta -October 5, 2007 +December 14, 2007 Author's address: [``http://www.cs.chalmers.se/~aarne`` http://www.cs.chalmers.se/~aarne] @@ -8,6 +8,7 @@ Author's address: % to compile: txt2tags -thtml --toc gfcc.txt History: +- 14 Dec 2007: simpler, Lisp-like concrete syntax of GFCC - 5 Oct 2007: new, better structured GFCC with full expressive power - 19 Oct: translation of lincats, new figures on C++ - 3 Oct 2006: first version @@ -53,7 +54,8 @@ will be used instead. GFC provides only marginal advantages as a target format compared with GF, and it is therefore just extra weight to carry around this format. -The main differences of GFCC compared with GFC (and GF) can be summarized as follows: +The main differences of GFCC compared with GFC (and GF) can be +summarized as follows: - there are no modules, and therefore no qualified names - a GFCC grammar is multilingual, and consists of a common abstract syntax together with one concrete syntax per language @@ -66,7 +68,8 @@ The main differences of GFCC compared with GFC (and GF) can be summarized as fol Here is an example of a GF grammar, consisting of three modules, -as translated to GFCC. The representations are aligned; thus they do not completely +as translated to GFCC. The representations are aligned; +thus they do not completely reflect the order of judgements in GFCC files, which have different orders of blocks of judgements, and alphabetical sorting. ``` |