Opened 9 years ago

Closed 9 years ago

#320 closed task (wontfix)

portability for g++ (GCC) 3.3.6

Reported by: jreed Owned by:
Priority: medium Milestone:
Component: build system Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

Few fixes for g++ (GCC) 3.3.6 portability. I will create branch for this.

Subtickets

Change History (4)

comment:1 Changed 9 years ago by jreed

Commit is r2832

comment:2 Changed 9 years ago by jinmei

I think the real first question is whether we should introduce workaround for this version of g++.

Providing workaround for broken environments is not necessarily a bad thing for wider adoption or for not losing existing customers, but at the same time reducing code readability and thus maintainability to help very minor environments that almost no one is using in practice is not a good deal especially for a longer term of view.

This is basically a tradeoff issue, and my personal impression from what I've heard is that the gain doesn't outweigh the disadvantage.

comment:3 Changed 9 years ago by jreed

  • Type changed from defect to task

comment:4 Changed 9 years ago by shane

  • Component changed from Unclassified to build system
  • Defect Severity set to N/A
  • Resolution set to wontfix
  • Status changed from new to closed
  • Sub-Project set to Core

GCC 3.3.6 was released in 2005:

http://gcc.gnu.org/releases.html

So it's 6 years old now. I don't see a compelling reason why someone can't upgrade to a 3.4.x or 4.x compiler. It's free, after all! :)

According to the main GCC page:

http://gcc.gnu.org/

4.3 is the oldest compiler still maintained, and it was released 4 years ago, so I don't think we need to worry too much about ancient versions of GCC.

So, unless someone asks for support or we get a patch, lets not worry about this.

Note: See TracTickets for help on using tickets.