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 encoding
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 `get-o
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 that
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 `call-with-o
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
`call-w
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")
(
6 matches
Mail list logo
