Dmitry Bogatov writes: > Documentation for vectors says: > Like lists, vectors have to be quoted: Which is wrong, vectors are self quoting. > Altho: > (define foo #((+ 1 2) 2)) > (eq? foo (eval foo (current-module))) ;; #t And that is a weird example you've chosen, as I don't expect eval to eval a vector, I'd have just printed it. > Am I missing something, or documentation is not in sync with current > state of art? The latter, though there is no penalty (performance or stylistic) if you are quoting your vectors. I've done a git grep though the docs, and there are a few referenes to it in texi files. - r5rs.texi should _not_ be change, since r5rs says vectors must be quoted. - guile.texi is autogenerated - api-evaluation.texi has an example in the section on quoting - api-compound.texi The last one is the only one that needs to be changed IMO. Most of the other references are in code or tests where they do no harm, but I'm not sure about vectors.c. There it appears in comments (which might be snarfed into guile.texi?) and one uncommented docstring. Is it worth changing? Patch attached that changes api-compound.texi. I split the paragraph to make it easier. -- Ian Price -- shift-reset.com "Programming is like pinball. The reward for doing it well is the opportunity to do it again" - from "The Wizardy Compiled"