From: Roland (roland.schwarz_at_[hidden])
Date: 2004-01-29 02:52:14
(Sean Kelly <sean_at_[hidden]>) wrote:
> What remains an issue in my mind is how far to take this. Socket and
> file classes for each platform at least... what else?
TTY, USB, FireWire, Parallel, .....?
Since file classes normaly also imply all other types of communication
resources this should be enough I think. But then different methods of
opening and parametizing need to be abstracted as well. Perhaps
by an ioctl method or similar? Or what about a library/framework where
the user optionally can plug in the system dependent low level part while
providing some implementation for the usual resources. This could be
done like the filebuffer concept in streams?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk