[cfe-dev] Status? Help Needed?

[Chris Lattner]

<cc'ing cfe-dev, please respond to the list, not me directly>

On Aug 19, 2007, at 9:47 PM, Ar18 at comcast.net wrote:
>> C++ support is a very, very, early state.  It is basically C with
>> bool, the C++ casts (static_cast etc), and some reference support.
> Thanks, I watched part of the video after I asked.
>
>>> * Also, what might be a general idea for when it might near a
>>> usable state (like less than 6 months, less than a year, less than
>>> 5 years, or)?
>> Right now, we don't have anyone seriously working on it.  I'd guess
>> 2-3 years, but "sooner if we have help" :).  We hope to have C very
>> solid over the next year.

> Does this also mean that you have nobody to work on it after the c  
> portion is done or does it just mean that you plan to start work on  
> it later?

We're actively looking for people to help with the C++ side.

> I guess what I'm getting at is... which of the following describes  
> your situation:
> 1) You are not planning to write a complete c++ frontend; the only  
> way it would get done is if someone would come along and do it
> or 2) You are planning to write one after the c part, but it would  
> be nice if you could get other people to help so it would get  
> finished faster.

#2.

> to it for some reason.  BTW, I don't suppose CINT has anything that  
> you could use, does it? http://root.cern.ch/twiki/bin/view/ROOT/CINT

I'm not sure, I hadn't seen CINT before.  However, C++ front-ends are  
complicated enough that you can't just take one out of one system and  
drop it into another.

>> If you're interested in non-coding tasks, I'd suggest using it to
>> compile lots of code (to find bugs), working on documentation,
> Regarding bug testing, Lord willing, I'll make a new post  
> referencing this and some more concepts.

Cool

>> compile lots of code (to find bugs), working on documentation,
> What kind of documentation?  Is there already a doc system set up,  
> or does that also need to be added to to the web page?

It's in the clang/doc tree.  The only doc we have so far is the  
internals manual.

>> If you're interested in non-coding tasks, I'd suggest using it to
>> compile lots of code (to find bugs), working on documentation,
>> working on the web page (http://clang.llvm.org is pretty sad ;-),
> Who do I contact about that?  Who handles the website?

I do, and this list does.  It is contained in the clang/www tree.

>> spreading the word to that might be interested, etc.
> Might be worth a try...  I'll need to be sure just what kind of  
> help you are looking for (you gave me a list already).

Great!

-Chris