path: root/hurd/translator.mdwn
diff options
authorThomas Schwinge <>2013-01-08 21:08:28 +0100
committerThomas Schwinge <>2013-01-08 21:08:28 +0100
commit160d0597cb94d58f8ab273226b1f3830589a500b (patch)
tree5502768f18d0f83acdeea820842cfbf1550b6ee3 /hurd/translator.mdwn
parent0a607c5c7bab130bfff70efd344bff78ce2bf88a (diff)
hurd/translator: Implementation languages.
Diffstat (limited to 'hurd/translator.mdwn')
1 files changed, 8 insertions, 2 deletions
diff --git a/hurd/translator.mdwn b/hurd/translator.mdwn
index 37f4e8b..e0baf13 100644
--- a/hurd/translator.mdwn
+++ b/hurd/translator.mdwn
@@ -1,5 +1,5 @@
-[[!meta copyright="Copyright © 2007, 2008, 2009, 2010, 2011, 2012 Free Software
-Foundation, Inc."]]
+[[!meta copyright="Copyright © 2007, 2008, 2009, 2010, 2011, 2012, 2013 Free
+Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -57,6 +57,12 @@ the socket API calls (which are mapped by [[glibc]] to equivalent RPC calls)*,
compared to *a [[libdiskfs]]-based translator implements a filesystem, based on
a backing store*.
+As a translator is not different from any other user-space application, it can
+be written in any programming language. The practicable constraint is that an
+interface suitable for doing [[RPC]]s should exist, which currently only exists
+for C ([[microkernel/mach/MIG]]). For Lisp, Perl, [[user/jkoenig/Java]] there
+so far are only experimental and incomplete implementations.
To learn how to write a translator, read the code!
It is well documented, in particular, the header files.
The [[Hurd_Hacking_Guide]] also has a tutorial.