> The # device syntax is very useful to mean the kernel device
> and none other in these situations.  There's definitely
> something unsatisfactory about it, but it works.

Smacks of overloading; at the very least it seems to suggest that
there ought to be official sanction as well as documented situations
exactly as you described.  To pepper the libraries with direct calls
to the kernel drivers is likely to cause consternation at the very
minimum.  I appreciate that a solution isn't yet obvious and I hope
that further thought will eventually lead to the necessary elegance.

++L


Reply via email to