Re: Support isEmptyStringInfo - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Re: Support isEmptyStringInfo
Date
Msg-id 20220324.103737.783084933568509720.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: Support isEmptyStringInfo  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At Wed, 23 Mar 2022 10:13:43 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote in 
> Robert Haas <robertmhaas@gmail.com> writes:
> > I think that the code is perfectly readable as it is and that this
> > change makes it less so.
> 
> Yeah, after a quick look through this patch I'm unimpressed too.
> The new code is strictly longer, and it requires the introduction
> of distracting "!" and "&" operators in many places.

The struct members are not private at all.  In that sense StringInfo
is not a kind of class of C/Java but like a struct of C/C++ at least
to me.  I think encapsulating only ".len == 0" doesn't help.  Already
in many places we pull out buf.data to use it separately from buf, we
have a dozen of instances of "buf.len (<|>|<=|>=) <some length>" and
even "buf.data[buf.len - 1] == '\n'"

About read-easiness, isEmptyStringInfo(str) slightly spins my eyes
than str->len == 0.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fix overflow in DecodeInterval
Next
From: "David G. Johnston"
Date:
Subject: Re: pg_stat_reset_single_*_counters vs pg_stat_database.stats_reset