Re: [OT] Re: Possible C++ safe header project - Re:[Criticism] On the discussion about C++ modules

2000-10-24 Thread Andreas Schwab
Timur Tabi <[EMAIL PROTECTED]> writes: |> ** Reply to message from Stephen Satchell <[EMAIL PROTECTED]> on |> Tue, 24 Oct 2000 09:54:46 -0700 |> |> |> > Linus has the final say, of course, but to suggest that any changes that |> > remove name collisions between C and C++ be rejected out of han

Re: [OT] Re: Possible C++ safe header project - Re:[Criticism] On the discussion about C++ modules

2000-10-24 Thread Timur Tabi
** Reply to message from Stephen Satchell <[EMAIL PROTECTED]> on Tue, 24 Oct 2000 09:54:46 -0700 > Linus has the final say, of course, but to suggest that any changes that > remove name collisions between C and C++ be rejected out of hand has the > potential for shooting ourselves in the foot.

Re: [OT] Re: Possible C++ safe header project - Re: [Criticism] On the discussion about C++ modules

2000-10-24 Thread Stephen Satchell
At 04:37 PM 10/23/00 +0200, Marko Kreen wrote: >* This will _not_ be accepted into standard codebase. Don't you >understand? Making headers C++ compatible is the first tiny >step for doing modules in C++. Yes, from driver/module >programmers perspective "they almost look same, and

[OT] Re: Possible C++ safe header project - Re: [Criticism] On the discussion about C++ modules

2000-10-23 Thread Marko Kreen
On Mon, Oct 23, 2000 at 08:47:53AM -0400, Linux Kernel Developer wrote: > Please comment on the pluses and minuses of each planned task and on > other things that you may see that should be done. Please no flames unless > they contain useful information. Also I plan to implement the first pa

Possible C++ safe header project - Re: [Criticism] On the discussion about C++ modules

2000-10-23 Thread Linux Kernel Developer
OK I've decided to give this a shot, IF there is sufficient interest out there for C++ safe headers. So all you coders out there who have tried and failed or who wish to program kernel modules in C++ join in and help out by listing the errors you have encountered with the current header setup