Sascha Ziemann writes:
> But quote from R7RS page 29:
>
>> For convenience and ease of use, the
>> global Scheme environment in a REPL must not be empty,
>> but must start out with at least the bindings provided by
>> the base library.
Yes I think it's a bug (or at least misleading) that using
Am So., 8. Jan. 2023 um 01:21 Uhr schrieb Robby Zambito
:
>
> In R7RS, the bytevector constructor is exported by (scheme base) (not (scheme
> bytevector)). It seems like the confusion is caused by --r7rs not evaluating
> in an environment that provides (scheme base).
>
Thanks, this helps!
But q
In R7RS, the bytevector constructor is exported by (scheme base) (not (scheme
bytevector)). It seems like the confusion is caused by --r7rs not evaluating in
an environment that provides (scheme base).
On 07.01.2023 22:12, Wolf wrote:
> On 2023-01-07 12:07:31 -0800, Matt Wette wrote:
>> On 1/7/23 8:34 AM, Sascha Ziemann wrote:
>>> Is the procedure "bytevector" missing in Guile?
>>>
>>> I tried this:
>>> guile --r7rs -c '(write (bytevector 1 2 3))'
>>>
>>> R7RS defines it on page 49.
>>>
>>
>> may
On 2023-01-07 12:07:31 -0800, Matt Wette wrote:
> On 1/7/23 8:34 AM, Sascha Ziemann wrote:
> > Is the procedure "bytevector" missing in Guile?
> >
> > I tried this:
> > guile --r7rs -c '(write (bytevector 1 2 3))'
> >
> > R7RS defines it on page 49.
> >
>
> maybe you need (import (rnrs bytevect
On 1/7/23 8:34 AM, Sascha Ziemann wrote:
Is the procedure "bytevector" missing in Guile?
I tried this:
guile --r7rs -c '(write (bytevector 1 2 3))'
R7RS defines it on page 49.
maybe you need (import (rnrs bytevectors))
Is the procedure "bytevector" missing in Guile?
I tried this:
guile --r7rs -c '(write (bytevector 1 2 3))'
R7RS defines it on page 49.
