[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I little help por improving the spanish translation of CLisp

Carlos Linares wrote in September:
 > As I told you I've finished the translation of CLisp. Anyway, there

 > 1.
 > In this message, what is bounded, the frame or the variables? I think
Variables are bound.
 > this message is referring to a frame where variables are bound, am I
 > wrong?
No you aren't.
 > "frame binding variables (~ = dynamically):"

 > 2.
 > `nested' have various meanings. It can mean that one thing is `into'
 > other one or that one thing is `joined' with other one. In this
Passing on this one.  Anybody?

 > 3.
 > I've been looking for FSUBR and SUBR through the whole world and I've
 > dedicated all my life!! :) However, I haven't found it? What are these
They related to very old implementations of Lisp.  IIRC, SUBR
(resp. FSUBR) served to recognize built-in functions (resp. special
forms or macros) in the symbol-function slot of symbols, for example
as (FSUBR <address>) so the Lisp interpreter knew it had to call an
internal procedure and would not evaluate the arguments, whereas
we all know (LAMBDA (#) ...).

The term of "signature" is used like in finance or crime: a kind of
characteristic of the function, and you know that when two signatures
differ, the functions must differ (if they are the same, the functions
need not be the same).  In CLISP, the signature of a function
comprises / encodes the parameter list (number of required / optional
parameters, &rest present and &key symbols).

 > 4.
 > Here, the question is similar to the first one. What is global, the
 > definition or the function? the definition, isn't it?
 > msgid "~: ~ has no global function definition"
The definition, for example using defun or defmacro vs. flet/labels

 > 5.
 > In this sentence, is #Y~ ok? shouldn't it read #~Y?
 > msgid "~ from ~: object #Y~ has not the syntax of a compiled closure"
I think it's ok as a closure is represented as #Y(..byte code..)

 > 6.
 > What do you want to mean with "plural loop keyword" and "singular loop
 > keyword"? I never heard of these terms before, ... Please, could you
See LOOP.LSP where this message comes from.
CLISP checks the grammar(!) and won't accept
	(loop for match being each external-symbols ...) or
	(loop for match being the  external-symbol ...)
See the trailing 's' for plural?            ------^

	Jo"rg Ho"hle.
Joerg.Hoehle@gmd.de	http://zeus.gmd.de/~hoehle/amiga-clisp.html