In comp.os.linux, article <C9pyMq.CI@bigcomm.gun.de>,
  ado@bigcomm.gun.de (Christoph Adomeit) writes:
quoted text
> 
> Correct me, if I'm wrong, I think C++ has a different symbol encoding e.g.
> for functions and structures. So it would be difficult to
... unless you tell the C++ compiler to use C encoding.
Unfortunately, you lose operator overloading that way.

quoted text
> a) search kernel-symbols via nlist()  and
Don't do that. Use a file in /proc instead. The additional kernel code is
minimal, it's _much_ easier to get the info with generic tools, and you're
protected when the kernel structure changes.

quoted text
> b) link .o Drivers (if one day there are some commercial ones), because they
> can't find some global symbols.
If the driver is compiled with the appropriate C++ headers it will link
without any problems.

-- 
Writing is not hard.  Just get paper and pencil, sit down and write it
as it occurs to you.  The writing is easy -- it's the occurring that's
hard.
                                -- Stephen Leacock
-- 
Matthias Urlichs -- urlichs@smurf.sub.org -- Phone: NONE; use email or lose.
Schleiermacherstrasse 12 -- 90491 Nuernberg -- Germany || Linux+Mac Consulting