| From: | Mark Dilger <hornschnorter(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Mark Dilger <hornschnorter(at)gmail(dot)com> |
| Subject: | typedef FileName not const? |
| Date: | 2016-09-28 00:08:24 |
| Message-ID: | 89ED0398-D022-4DED-82EF-E0A9D4DA9B7E@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Friends,
along the lines of other similar emails from me of late,
I tried to avoid casting away const when using the FileName
typedef. There are several calls where a (const char *) has to
be cast to (char *) due to FileName being typedef'd as
non-const. But changing the typedef to const doesn't seem to
conflict with any code in the source tree.
Since this may be seen as an external API change, I kept
these changes in their own patch submission, so that it can
be rejected separately if need be.
Mark Dilger
| Attachment | Content-Type | Size |
|---|---|---|
| filename.patch.1 | application/octet-stream | 2.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-09-28 00:16:07 | Re: typedef FileName not const? |
| Previous Message | Mark Dilger | 2016-09-28 00:01:48 | casting away const in comparators |