Commit ec05bafd authored by Tom Lane's avatar Tom Lane

Put "inline" marker on declarations of inline functions.

I'm having a hard time telling whether the letter of the C standard
requires this, but we do have a couple of buildfarm members that
throw warnings when this is not done.  Oversight in c532d15d.
parent 8818ad5b
...@@ -114,8 +114,8 @@ static Datum CopyReadBinaryAttribute(CopyFromState cstate, FmgrInfo *flinfo, ...@@ -114,8 +114,8 @@ static Datum CopyReadBinaryAttribute(CopyFromState cstate, FmgrInfo *flinfo,
/* Low-level communications functions */ /* Low-level communications functions */
static int CopyGetData(CopyFromState cstate, void *databuf, static int CopyGetData(CopyFromState cstate, void *databuf,
int minread, int maxread); int minread, int maxread);
static bool CopyGetInt32(CopyFromState cstate, int32 *val); static inline bool CopyGetInt32(CopyFromState cstate, int32 *val);
static bool CopyGetInt16(CopyFromState cstate, int16 *val); static inline bool CopyGetInt16(CopyFromState cstate, int16 *val);
static bool CopyLoadRawBuf(CopyFromState cstate); static bool CopyLoadRawBuf(CopyFromState cstate);
static int CopyReadBinaryData(CopyFromState cstate, char *dest, int nbytes); static int CopyReadBinaryData(CopyFromState cstate, char *dest, int nbytes);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment