"Dale P. Smith" wrote: > > I don't thing gensym is right yet. > > There are about a dozen or so places in calling.scm where gensym is used > with a symbol, I thought recent changes required the first argument to > be a string. Trying it out, I find: > > guile> (gensym "foo") > > Backtrace: > 0* [gsubr-apply #<primitive-procedure gensym> "foo"] > > ERROR: In procedure gsubr-apply in expression (gensym "foo"): > ERROR: Wrong type argument in position 1 (expecting SYMBOLP): "foo" > ABORT: (wrong-type-arg) > > guile> (gensym 'foo) > > Backtrace: > 0* [gsubr-apply #<primitive-procedure gensym> foo] > > ERROR: In procedure gsubr-apply in expression (gensym (quote foo)): > ERROR: Wrong type argument: foo > ABORT: (wrong-type-arg) > > guile> (gensym (string->symbol "foo")) > > Backtrace: > 0* [gsubr-apply #<primitive-procedure gensym> foo] > > ERROR: In procedure gsubr-apply in expression (gensym (string->symbol > "foo")): > ERROR: Wrong type argument: foo > ABORT: (wrong-type-arg) > > -Dale > > -- > Dale P. Smith > Altus Technologies Corp. > [EMAIL PROTECTED] > 400-746-9000 x309 -- Dale P. Smith Altus Technologies Corp. [EMAIL PROTECTED] 400-746-9000 x309
