Introducing cfe-users mailing list!

By popular demand, the cfe-users list has been created. This list will be used for those who need help using Clang.

You may subscribe here:
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-users

I hope that many of our cfe-dev subscribers will also subscribe to cfe-users and help answer questions there as well.

If anyone wants to properly document this list on the website, please go ahead and propose some changes. I have added it to the sidebar, but I think having a general description of the lists and which to use would be useful. We do not have a good place for that at the moment.

Thanks,
Tanya Lattner

Quick, before it's too late!: call it `clang-users`.

"those who need help using clang" are the ones who most need to *not*
be confused by `cfe-`. For the sake of our users, please rename this;
it adds an extra step of confusion that would simply "disappear" if it
were named appropriately. Also, names should be self-documenting :slight_smile:

-- Sean Silva

Quick, before it's too late!: call it `clang-users`.

I agree. +1.

Calling it cfe-users is consistent with our other clang mailing lists. When the mailing lists are *all* moved of mail.cs.uiuc.edu, we'll rename all the clang lists to be clang-* instead of cfe-*. In the meantime, consistency is good.

-Chris

For what it's worth, it seems to me that "clang" as the C/C++ compiler is cfe+llvm, then why would it be more consistent to name it cfe-users than llvm-users?
Obviously since this list intends to target people using "clang" as in the binary and *not* clang is the "clang-cfe", I second Sean Silva on the name.

My 2 cents,

Mehdi

What about users of cfe (C++ or C API) itself for AST analysis?
Where should such questions go?

I thought it was still cfe-dev@, but I was maybe wrong on the goal of this new list? Indeed if it is intended for people using clang-cfe APIs to build tools then I understand Chris' point and I was off-topic :wink:

Best,

Mehdi

Consistency is good if it means that comprehension comes faster, not as an objective in itself. For an existing clang developer, you can safely assume that they know that cfe and clang are interchangeable. But why would a new clang user with questions assume that cfe means clang? It is not important that a new user realises that they can join the cfe-* lists if they want to do development work, because by the time that they are ready to contribute they should understand that clang is an LLVM front end and not just a gcc replacement. It is important that they are able to understand that they have found the list that they are looking for and that is much more likely if it is called clang-users than cfe-users.

David

Calling it cfe-users is consistent with our other clang mailing lists. When the mailing lists are *all* moved of mail.cs.uiuc.edu, we'll rename all the clang lists to be clang-* instead of cfe-*. In the meantime, consistency is good.

Consistency is good if it means that comprehension comes faster, not as an objective in itself. For an existing clang developer, you can safely assume that they know that cfe and clang are interchangeable. But why would a new clang user with questions assume that cfe means clang? It is not important that a new user realises that they can join the cfe-* lists if they want to do development work, because by the time that they are ready to contribute they should understand that clang is an LLVM front end and not just a gcc replacement. It is important that they are able to understand that they have found the list that they are looking for and that is much more likely if it is called clang-users than cfe-users.

One could argue that you already have this problem with new people and they seem to find cfe-dev just fine. But I'm not saying the name is perfect, but just having the list is a step in the right direction. cfe-users is for people who are using it as a compiler. Not people who are creating tools or using APIs.. thats development and therefore cfe-dev.The User's guide should be update to mention the list. (Clang Compiler User’s Manual — Clang 18.0.0git documentation). If no one else does it, I will eventually get to it.

This was already discussed many months ago on the list and it was decided to go with cfe-users, so thats why the list was created. I just finally got around to announcing it since the dev-meeting stuff cleared off my plate.

-Tanya