pgsql: Fix volatile vs. pointer confusion

2019-03-15 Thread Peter Eisentraut
Fix volatile vs. pointer confusion Variables used after a longjmp() need to be declared volatile. In case of a pointer, it's the pointer itself that needs to be declared volatile, not the pointed-to value. So we need PyObject *volatile items; instead of volatile PyObject *items; /* w

pgsql: Fix volatile vs. pointer confusion

2019-03-15 Thread Peter Eisentraut
Fix volatile vs. pointer confusion Variables used after a longjmp() need to be declared volatile. In case of a pointer, it's the pointer itself that needs to be declared volatile, not the pointed-to value. So we need PyObject *volatile items; instead of volatile PyObject *items; /* w

pgsql: Fix volatile vs. pointer confusion

2019-03-15 Thread Peter Eisentraut
Fix volatile vs. pointer confusion Variables used after a longjmp() need to be declared volatile. In case of a pointer, it's the pointer itself that needs to be declared volatile, not the pointed-to value. So we need PyObject *volatile items; instead of volatile PyObject *items; /* w

pgsql: Fix volatile vs. pointer confusion

2019-03-15 Thread Peter Eisentraut
Fix volatile vs. pointer confusion Variables used after a longjmp() need to be declared volatile. In case of a pointer, it's the pointer itself that needs to be declared volatile, not the pointed-to value. So we need PyObject *volatile items; instead of volatile PyObject *items; /* w

pgsql: Fix volatile vs. pointer confusion

2019-03-14 Thread Peter Eisentraut
Fix volatile vs. pointer confusion Variables used after a longjmp() need to be declared volatile. In case of a pointer, it's the pointer itself that needs to be declared volatile, not the pointed-to value. So we need PyObject *volatile items; instead of volatile PyObject *items; /* w