1 May
2010
1 May
'10
10:36 p.m.
On Thu, Jan 14, 2010 at 9:30 AM, Leslie P. Polzer sky@viridian-project.de wrote:
A minor nit I found while passing a custom encoding to this function. It's quite cumbersome to have to specify the other optional arguments to this function just to change one of them.
FOREIGN-STRING-TO-LISP does take keyword arguments. What am I missing?
--
Luís Oliveira
http://r42.eu/~luis/