const qualifier for list APIs - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject const qualifier for list APIs
Date
Msg-id CAExHW5sGRMU_Vypqr9tQaDwmFmkSj+Km6X8NxzA7HBa7JbZ=ig@mail.gmail.com
Whole thread Raw
Responses Re: const qualifier for list APIs
List pgsql-hackers
Hi All,
Functions like lappend_*() in list.c do not modify the second
argument. So it can be qualified as const. Any reason why we don't do
that? Is it because the target pointer ptr_value is not const
qualified?

In my code, I am using lappend() and passing it the output of
pq_getmsgstring() which returns const char *. The list is used to just
collect these pointers to be scanned later a few times within the same
function. So there is no possibility of freeing or changing area
within the StringInfo. So the coding practice though questionable, is
safe and avoids unnecessary pallocs. But SonarQube does complain about
it.

-- 
Best Wishes,
Ashutosh Bapat



pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Report checkpoint progress with pg_stat_progress_checkpoint (was: Report checkpoint progress in server logs)
Next
From: Yugo NAGATA
Date:
Subject: Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands