[llvm-dev] [RFC] Renaming f18....
Chris Lattner via llvm-dev
llvm-dev at lists.llvm.org
Mon May 6 21:00:58 PDT 2019
> On Apr 30, 2019, at 2:02 PM, David Greene via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> "Finkel, Hal J. via llvm-dev" <llvm-dev at lists.llvm.org> writes:
>
>> On 4/30/19 9:33 AM, David Greene via llvm-dev wrote:
>>> "fortran" seems far too generic to me. What distinguishes it from a
>>> different Fortran compiler?
>>>
>>> What about "flange" (Fortran language environment)? It's distinct from
>>> the already-in-use-by-two-projects "flang" yet fits in with the existing
>>> "clang" naming scheme. Plus it captures the fact that the Fortran
>>> runtime is a rather large piece of work.
>>
>>
>> I think that we should call the project flang and the name of the drive
>> should also be flang. With all due respect to the other projects called
>> flang, and I've been involved in at least two of them, the goal has
>> always been to have an upstream fortran compiler called flang, and if
>> this is our upstream fortran compiler, it should be called flang.
>>
>> The fact that the Clang mailing list is called cfe-dev, etc. instead of
>> clang-dev, etc. is confusing to those outside of the community. I think
>> that we should not repeat that kind of difference, and we should name
>> the mailing lists, directories, etc. based on "flang" as well.
>
> +100
>
> I only suggested a different name because I assumed a different name was
> desired.
My opinion should be weighted weakly here, but I am also +1 on “flang”. I completely agree with Hal that the cfg-dev vs clang-dev naming thing was a mistake, and hopefully the cfe repo will get renamed to clang as well with the GitHub move.
-Chris
More information about the llvm-dev
mailing list