[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Improve error reporting when serializing non-Unicode strings
|
From: |
Eli Zaretskii |
|
Subject: |
Re: [PATCH] Improve error reporting when serializing non-Unicode strings to JSON |
|
Date: |
Sat, 23 Dec 2017 15:44:31 +0200 |
> From: Philipp Stephani <address@hidden>
> Date: Sat, 23 Dec 2017 12:33:46 +0000
> Cc: address@hidden, address@hidden
>
> This patch only improves the error symbol when trying to serialize a
> non-Unicode string to JSON. Right now
> this raises "out of memory", which is somewhat confusing. This patch improves
> this to raise
> "wrong-type-argument".
OK, but why do we need external functions for doing that? What is
missing in our own code to detect such a situation?
- [PATCH] Improve error reporting when serializing non-Unicode strings to JSON, Philipp Stephani, 2017/12/22
- Re: [PATCH] Improve error reporting when serializing non-Unicode strings to JSON, Eli Zaretskii, 2017/12/23
- Re: [PATCH] Improve error reporting when serializing non-Unicode strings to JSON, Philipp Stephani, 2017/12/23
- Re: [PATCH] Improve error reporting when serializing non-Unicode strings to JSON, Philipp Stephani, 2017/12/23
- Re: [PATCH] Improve error reporting when serializing non-Unicode strings to JSON, Eli Zaretskii, 2017/12/23
- Re: [PATCH] Improve error reporting when serializing non-Unicode strings to JSON, Philipp Stephani, 2017/12/23
- Re: [PATCH] Improve error reporting when serializing non-Unicode strings to JSON, Eli Zaretskii, 2017/12/23
- Re: [PATCH] Improve error reporting when serializing non-Unicode strings to JSON, Philipp Stephani, 2017/12/23
- [PATCH] Improve error reporting when serializing non-Unicode strings to JSON, Philipp Stephani, 2017/12/23