On Fri, 2014-03-14 at 11:51 -0400, Mark H Weaver wrote:
> Diogo Ramos writes:
>
> > Is it possible to have a number as a module-name component?
> >
> > e.g. (define-module (42 bar))
>
> At present, module name components must be symbols. However, R7RS
> allows either symbols or exact non-negati
"Diogo F. S. Ramos" writes:
>>> Is it possible to have a number as a module-name component?
>>>
>>> e.g. (define-module (42 bar))
>>
>> At present, module name components must be symbols.
>
> Could I use something like (define-module (#{42}# bar))?
I don't see why not. Also, you can always try
>> Is it possible to have a number as a module-name component?
>>
>> e.g. (define-module (42 bar))
>
> At present, module name components must be symbols.
Could I use something like (define-module (#{42}# bar))?
Diogo Ramos writes:
> Is it possible to have a number as a module-name component?
>
> e.g. (define-module (42 bar))
At present, module name components must be symbols. However, R7RS
allows either symbols or exact non-negative integers to be module name
components, so it seems likely that we'll
On Thu, 2014-03-13 at 23:52 -0300, Diogo Ramos wrote:
> Is it possible to have a number as a module-name component?
>
> e.g. (define-module (42 bar))
>
Current try-module-autoload will call symbol->string to convert all the
module-name to a module path for loading.
e.g '(a b) ==> _default_load_p
Is it possible to have a number as a module-name component?
e.g. (define-module (42 bar))
