[llvm-dev] [RFC] Renaming f18....

[David Greene via llvm-dev]

"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.

                          -David

Stephen Scalpone via llvm-dev <llvm-dev at lists.llvm.org> writes:

> On 4/10/19, 12:15 PM, "llvm-dev on behalf of Chris Lattner via llvm-dev" wrote:
>
>> The foundation recommends considering a new name for the project (e.g. flang or simply fortran)
>
>>  to be more accessible and obvious for new contributors - in addition to being the repository name,
>
>>  it will also  be the base stem for mailing lists and other project related material.  The f18 folks can
>
>> discuss this, come up with a decision, and work with the llvm-admin team to set up the requisite infra.
>
>  
>
> We'd like to recommend "fortran" as the name of the source repository, mailing list (fortran-dev), and the C++ namespace.  The source code is all about Fortran so
> people working on the compiler and tools will be thinking fortran first and foremost.
>
>  
>
> As for the driver, time will tell.  I expect the f18 developers at Arm will post an RFC asking for advice about how to write the driver.  Base it on clang or start fresh? 
> Extract the clang driver into its own project?  Name it flang?  But that's another RFC.
>
>  
>
> Thanks in advance for your feedback,
>
>  
>
> - Steve
>
>  
>
> ---------------------------------------------------------------------------------------------------------------------------------
> This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or
> distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. 
> ---------------------------------------------------------------------------------------------------------------------------------
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev