I think your 32-bit options at this point are these:
1) Use one of the nightly builds, e.g.
https://plt.cs.northwestern.edu/snapshots/
2) Compile it yourself, using the source bundle.
3) (Of course, you could use an older version. Looks ilke 7.3 is the last one
released in a 32-bit Linux
On 2/16/21, Dominik Pantůček wrote:
>
> On 16. 02. 21 22:27, Matthew Flatt wrote:
>> At Tue, 16 Feb 2021 16:03:29 -0500, Ben Greenman wrote:
>>> Sadly, I've already compressed a few files using
>>> `call-with-output-string` ... is there an easy way to decompress those
>>> / undo the UTF-8
On Tue, Feb 16, 2021 at 12:26:50PM -0500, John Clements wrote:
> Help me out: which platform are you referring to?
The Linux one that was on everybody's PC before PC's went 64-bit.
I still use that old computer now and then with a stable
Devuan release, especially when I'm on the move.
(though
On 16. 02. 21 22:27, Matthew Flatt wrote:
> At Tue, 16 Feb 2021 16:03:29 -0500, Ben Greenman wrote:
>> Sadly, I've already compressed a few files using
>> `call-with-output-string` ... is there an easy way to decompress those
>> / undo the UTF-8 encoding?
>
> Unfortunately, the underlying
At Tue, 16 Feb 2021 16:03:29 -0500, Ben Greenman wrote:
> Sadly, I've already compressed a few files using
> `call-with-output-string` ... is there an easy way to decompress those
> / undo the UTF-8 encoding?
Unfortunately, the underlying `get-output-string` conversion is lossy,
because bytes
On 2/16/21, Matthew Flatt wrote:
> At Tue, 16 Feb 2021 15:44:54 -0500, Ben Greenman wrote:
>> But in my compressed string, the second
>> byte is #o357 for some reason. I'm not sure how that could have
>> happened ... some kind of encoding issue with string ports?
>
> Yes.
>
> You want
At Tue, 16 Feb 2021 15:44:54 -0500, Ben Greenman wrote:
> But in my compressed string, the second
> byte is #o357 for some reason. I'm not sure how that could have
> happened ... some kind of encoding issue with string ports?
Yes.
You want `call-with-output-bytes` on the compress size and
I was able to use the Bootstrap teachpack. I am running my program from the
command line and racket returns *#*. Is there a way to view the
output outside of Dr. Racket?
On Sunday, February 7, 2021 at 4:51:27 PM UTC-5 Robby Findler wrote:
> Okay, I've added it. It is pretty straightforward to
I'm trying to use `gzip-through-ports` and I haven't been able to
unzip compressed data.
Here's a tiny example. I think this should print "hello world":
```
#lang racket
(require
(only-in file/gzip gzip-through-ports)
(only-in file/gunzip gunzip-through-ports))
(define src "hello world")
Help me out: which platform are you referring to?
John
> On Feb 16, 2021, at 8:10 AM, Hendrik Boom wrote:
>
> On Sat, Feb 13, 2021 at 09:17:26PM -0500, 'John Clements' via Racket Users
> wrote:
>> *** Racket 8.0 is here! ***
>>
>> Racket version 8.0 is now available from
>>
>>
On Sat, Feb 13, 2021 at 09:17:26PM -0500, 'John Clements' via Racket Users
wrote:
> *** Racket 8.0 is here! ***
>
> Racket version 8.0 is now available from
>
> https://racket-lang.org/
Are there no 32-bit intel binaries available?
Or did I just look too soon?
-- hendrik
--
You received
Hi all,
Issue 46 is here: https://racket-news.com/2021/02/racket-news-issue-46.html
Take a look and enjoy!
--
Paulo Matos
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send
So exciting! A massive thank you to everyone making Racket even better. :)
~slg
‐‐‐ Original Message ‐‐‐
On Saturday, February 13, 2021 9:17 PM, 'John Clements' via Racket Users
wrote:
> *** Racket 8.0 is here! ***
>
> Racket version 8.0 is now available from
>
>
13 matches
Mail list logo
