Re: Pass a serial port as user data in a GTK callback handler?

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Sat, 15 Feb 2014 21:32:58 -0200, hreba wrote:

> My actual programming exercise has a GTK GUI, and I want a callback 
> handler to communicate through a serial port, so I need to pass the port 
> in my user data, which must be of

Additionally to other responses.

There cannot be any reason to pass a stream object to GTK signal handler.
It is most certainly wrong to do any I/O from a signal handler, as it would
block the UI.

In some cases the UI may indeed be aware of I/O objects, like a COM port
configuration dialog or cancel button. In these cases there is a larger
object that contains the I/O object usually as a private member.

Specifically to GTK, you should better use smart pointers rather than raw
access types when dealing with callbacks and pass them around. The point
that UI and I/O will run in independent tasks. It is difficult to prevent
dangling pointers otherwise. [I don't consider global variables, of course]

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de