Currently it's perfectly legit to configure w/ --enable-exceptions even though mozilla doesn't use them at all. In fact, building w/ exceptions causes many extra megabytes of bloat on linux. If we remove it from configure, at least we don't look like we're promoting it's use.
I'm going to assume that anyone who uses this option knows about the bloat that they are accuring. If I'm not mistaken, you need to build mozilla components with exceptions in order to use them in other programs that use exceptions, right? If that's the case, I don't see the point of making it harder for people to compile with exceptions by removing this option. The big rtti/exceptions discussion in the newsgroup appears to have gone off on a tangent. Is there anything else I'm missing about the need to remove this option?
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.