Re: Refactoring base64 encoding and decoding into a safer interface
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-07-02T08:22:29Z
Lists: pgsql-hackers
On Tue, Jul 02, 2019 at 09:56:03AM +0200, Daniel Gustafsson wrote: > I’m not sure we need to go to that length, but I don’t have overly strong > opinions. I think of this more like a case of “we’ve changed the API with new > errorcases that we didn’t handle before, so we’re being a little defensive to > help you avoid subtle bugs”. I quite like this suggestion. > Looks good, passes tests, provides value to the code. Bumping this to ready > for committer as I no more comments to add. Thanks. I'll look at that again in a couple of days, let's see if others have any input to offer. -- Michael
Commits
-
Introduce safer encoding and decoding routines for base64.c
- cfc40d384ae5 13.0 landed