Announcement

Collapse
No announcement yet.

GCC 7 To End Feature Development Next Month

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • GCC 7 To End Feature Development Next Month

    Phoronix: GCC 7 To End Feature Development Next Month

    Friday's GCC 7 status report indicates the feature freeze is coming up in just a few weeks...

    http://www.phoronix.com/scan.php?pag...-3-Coming-Soon

  • #2
    I read that as
    "GCC To End Feature Development Next Month"
    instead of
    "GCC 7 status report indicates the feature freeze is coming"

    Clearly more coffee is needed.

    Coffee++

    Comment


    • #3
      Originally posted by ElectricPrism View Post
      I read that as
      "GCC To End Feature Development Next Month"
      instead of
      "GCC 7 status report indicates the feature freeze is coming"

      Clearly more coffee is needed.

      Coffee++
      No way, they're removing Java. I heard GCC developers are planning to add Ceylan language, a name inspired on a known tea type. They're tea drinkers, damn britphilia...

      Comment


      • #4
        Originally posted by timofonic View Post

        No way, they're removing Java. I heard GCC developers are planning to add Ceylan language, a name inspired on a known tea type. They're tea drinkers, damn britphilia...
        Many(most?) gcc developers are employed by Red Hat now, wouldn't be surprising if they did add Ceylon.

        Comment


        • #5
          Originally posted by timofonic View Post
          No way, they're removing Java.
          In my opinion, removal of Java is a direct consequence of GCC not being able to seamlessly create programs where C/C++ and Java can call each other. Something like .NET is missing.

          A conceptual example:

          Code:
          $ cat a.cc
          #include "Cls.java"
          int main() {
            std::cout << (new Cls()).j() << std::endl;
          }
          int c() { return 3; }
          
          $ cat a.h
          int c();
          
          $ cat Cls.java
          import "a.h"
          class Cls {
            int j() { return 2+c(); }
          }
          
          $ gcc a.cc Cls.java -o cj
          $ ./cj
          5
          GCC fails to deliver Java-C interoperability --> removing Java from GCC --> many years into the future some project other than GCC will deliver it.

          It's doable.

          Comment


          • #6
            Originally posted by atomsymbol View Post
            GCC fails to deliver Java-C interoperability --> removing Java from GCC --> many years into the future some project other than GCC will deliver it.

            It's doable.
            Plenty of things are doable and theoretically possible, but unless somebody puts his money where his mouth is, nothing happens. You are welcome to join as a GCJ developer.

            Comment


            • #7
              Originally posted by peppercats View Post
              Many(most?) gcc developers are employed by Red Hat now, wouldn't be surprising if they did add Ceylon.
              Red Hat + gcc + Ceylon --> Cylon

              It all makes sense now. Don your tin hats plz.

              Comment


              • #8
                Originally posted by atomsymbol View Post

                In my opinion, removal of Java is a direct consequence of GCC not being able to seamlessly create programs where C/C++ and Java can call each other. Something like .NET is missing.

                A conceptual example:

                Code:
                $ cat a.cc
                #include "Cls.java"
                int main() {
                std::cout << (new Cls()).j() << std::endl;
                }
                int c() { return 3; }
                
                $ cat a.h
                int c();
                
                $ cat Cls.java
                import "a.h"
                class Cls {
                int j() { return 2+c(); }
                }
                
                $ gcc a.cc Cls.java -o cj
                $ ./cj
                5
                GCC fails to deliver Java-C interoperability --> removing Java from GCC --> many years into the future some project other than GCC will deliver it.

                It's doable.
                gcj was just coderot, there was nobody to maintain it and it didn't serve much of a purpose anymore.

                GCC needs simplified as much as possible, not complicated.

                Comment


                • #9
                  GCJ was a great idea and might have helped cause the release of OpenJDK leading to Icedtea

                  Comment

                  Working...
                  X