PgFlush

On Photon 1.14 what could make PgFlush return an error (-1) with errno set
to 35 (ENOMSG).

  • Mario

Mario Charest wrote:

On Photon 1.14 what could make PgFlush return an error (-1) with errno set
to 35 (ENOMSG).

It’s not an error – it has the same meaning as it has for
PhEventEmit(). I don’t know why it’s documented for PhEventEmit() but
not for PgFlush() – perhaps fewer people check the result of PgFlush()
than PhEventEmit()…

“Wojtek Lerch” <Wojtek_L@yahoo.ca> wrote in message
news:cu090q$726$1@inn.qnx.com

Mario Charest wrote:
On Photon 1.14 what could make PgFlush return an error (-1) with errno
set to 35 (ENOMSG).

It’s not an error – it has the same meaning as it has for PhEventEmit().
I don’t know why it’s documented for PhEventEmit() but not for
PgFlush() – perhaps fewer people check the result of PgFlush() than
PhEventEmit()…

It’s not documented on QNX6 SP1 either.

Mario Charest wrote:

“Wojtek Lerch” <> Wojtek_L@yahoo.ca> > wrote in message
news:cu090q$726$> 1@inn.qnx.com> …

Mario Charest wrote:

On Photon 1.14 what could make PgFlush return an error (-1) with errno
set to 35 (ENOMSG).

It’s not an error – it has the same meaning as it has for PhEventEmit().
I don’t know why it’s documented for PhEventEmit() but not for
PgFlush() – perhaps fewer people check the result of PgFlush() than
PhEventEmit()…


It’s not documented on QNX6 SP1 either.

I don’t think it happens on QNX6 – does it?

“Wojtek Lerch” <Wojtek_L@yahoo.ca> wrote in message
news:cu0sgh$726$2@inn.qnx.com

Mario Charest wrote:
“Wojtek Lerch” <> Wojtek_L@yahoo.ca> > wrote in message
news:cu090q$726$> 1@inn.qnx.com> …

Mario Charest wrote:

On Photon 1.14 what could make PgFlush return an error (-1) with errno
set to 35 (ENOMSG).

It’s not an error – it has the same meaning as it has for PhEventEmit().
I don’t know why it’s documented for PhEventEmit() but not for
PgFlush() – perhaps fewer people check the result of PgFlush() than
PhEventEmit()…


It’s not documented on QNX6 SP1 either.

I don’t think it happens on QNX6 – does it?

Don’t know, never bother to test return value :wink: But this contract has
strict requirement, ergo the extra error handling.

Wojtek Lerch <Wojtek_L@yahoo.ca> wrote:

Mario Charest wrote:
On Photon 1.14 what could make PgFlush return an error (-1) with errno set
to 35 (ENOMSG).

It’s not an error – it has the same meaning as it has for
PhEventEmit(). I don’t know why it’s documented for PhEventEmit() but
not for PgFlush() – perhaps fewer people check the result of PgFlush()
than PhEventEmit()…

I’ve noted this as something to fix if we ever release a new version of
the Photon 1.14 docs.


Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

“Steve Reid” <stever@sreid.ott.qnx.com> wrote in message
news:cu88r5$72t$1@inn.qnx.com

Wojtek Lerch <> Wojtek_L@yahoo.ca> > wrote:
Mario Charest wrote:
On Photon 1.14 what could make PgFlush return an error (-1) with errno
set
to 35 (ENOMSG).

It’s not an error – it has the same meaning as it has for
PhEventEmit(). I don’t know why it’s documented for PhEventEmit() but
not for PgFlush() – perhaps fewer people check the result of PgFlush()
than PhEventEmit()…

I’ve noted this as something to fix if we ever release a new version of
the Photon 1.14 docs.

Not sure if you missed it but it’s also missing for QNX6.3


Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems

Mario Charest wrote:

“Steve Reid” <> stever@sreid.ott.qnx.com> > wrote in message
I’ve noted this as something to fix if we ever release a new version of
the Photon 1.14 docs.


Not sure if you missed it but it’s also missing for QNX6.3

Mario, it’s supposed to be missing from the QNX 6.3 docs. It doesn’t
happen in 6.3.

“Wojtek Lerch” <Wojtek_L@yahoo.ca> wrote in message
news:cu8bsv$de$1@inn.qnx.com

Mario Charest wrote:
“Steve Reid” <> stever@sreid.ott.qnx.com> > wrote in message
I’ve noted this as something to fix if we ever release a new version of
the Photon 1.14 docs.


Not sure if you missed it but it’s also missing for QNX6.3

Mario, it’s supposed to be missing from the QNX 6.3 docs.
not (?)



It doesn’t happen in 6.3.

Oh I see, sorry about that.