X-Git-Url: https://git.stderr.nl/gitweb?a=blobdiff_plain;f=docs%2Freference%2Fglk-introduction.sgml;h=aeacbec18fbbe655169157ef1e6caa5bb59bf4cf;hb=c4142afddd5b220686eb64c4bd346a722f9e20c1;hp=ec2897934c1a1d1549cc1cad9dd1b74dfcbcc7e1;hpb=70f337d7209f9a26522b66f267b09658c60f4c17;p=projects%2Fchimara%2Fchimara.git diff --git a/docs/reference/glk-introduction.sgml b/docs/reference/glk-introduction.sgml index ec28979..aeacbec 100644 --- a/docs/reference/glk-introduction.sgml +++ b/docs/reference/glk-introduction.sgml @@ -45,7 +45,7 @@ You can think of Glk as an IF virtual machine, without the virtual machine part. An IF virtual machine has been designed specifically to go along with Glk. This VM, called Glulx, uses Glk as its interface; each Glk call corresponds to an input/output opcode of the VM. -For more discussion of this approach, see Glk and the Virtual Machine. Glulx is documented at http://www.eblong.com/zarf/glulx. +For more discussion of this approach, see Glk and the Virtual Machine. Glulx is documented at http://eblong.com/zarf/glulx. Of course, Glk can be used with other IF systems. The advantage of Glulx is that it provides the game author with direct and complete access to the Glk API. Other IF systems typically have an built-in abstract I/O API, which maps only partially onto Glk. For these systems, Glk tends to be a least-common-denominator interface: highly portable, but not necessarily featureful. (Even if Glk has a feature, it may not be available through the layers of abstraction.)