msyds/gf-core
1
0
Fork 0
forked from GitHub/gf-core
Code Pull Requests Activity

just module rules missing

Browse Source
This commit is contained in:
aarne
2005-04-10 15:57:33 +00:00
parent 792fea08bd
commit dc0ec11e28
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
doc/gf-modules.html
View File

@@ -749,11 +749,23 @@ times. Here is a summary of how they are compiled:
</ul> </ul>
This means that some generated code is duplicated, because those operations that This means that some generated code is duplicated, because those operations that
do have complete definitions in an <tt>interface</tt> are copied to each of do have complete definitions in an <tt>interface</tt> are copied to each of
the <tt>instances</tt> the <tt>instances</tt>.
<h3>Transfer modules</h3> <h3>Transfer modules</h3>
<b>Translation by transfer</b> means that syntax trees are manipulated
by non-compositional functions (<b>transfer rules</b>) between the
source and target languages. They are being introduce to GF as a module
type of its own, but their development is still in progress. What
will be available are <i>at least</i> <tt>fun</tt> and <tt>def</tt>
judgements, but more is needed. It has not yet been defined how
transfer modules are integrated in multilingual grammars, i.e.\
where in the grammar it is specified what transfer to use.
(Both GF and GFC have a syntax for transfer modules and
multilingual headers, but their compilation further than parsing
has not been implemented.)
<h2>Summary of module syntax and semantics</h2> <h2>Summary of module syntax and semantics</h2>