You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by ji...@apache.org on 2004/05/13 17:46:56 UTC

[jira] Created: (XERCESC-1212) Xerces-C Conflicts with fdlibm: enum names too common

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESC-1212

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESC-1212
    Summary: Xerces-C Conflicts with fdlibm: enum names too common
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Xerces-C++
 Components: 
             Utilities
             Validating Parser (DTD)
             Validating Parser (Schema) (Xerces 1.5 or up only)
   Versions:
             2.5.0

   Assignee: 
   Reporter: Robert Buck

    Created: Thu, 13 May 2004 8:46 AM
    Updated: Thu, 13 May 2004 8:46 AM
Environment: ALL

Description:
For those developers that use the freely distributable math library, or fdlibm, a conflict exists between the definition of UNKNOWN. Specifically, if you include fdlibm headers prior to xerces-c headers, xerces-c user applications will not compile.

Choosing common names such as UNKNOWN is not helpful to those of us that link in many third-party libraries, since the likelihood that a conflict will exist with such a name is greatly increased. Please prefix the names with something that distinguishes the enum value as being from Xerces-C. In the very least, set it as a standard practice in future enum types to use more conspicuous names. It would be nice if you changed these before these names get entrenched in C++ user code.

I do have a work-around, but it's rather ugly. I just raise this to your attention, mostly to suggest the adoption of such a coding practice.

Thanks


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org

[jira] Commented: (XERCESC-1212) Xerces-C Conflicts with fdlibm: enum names too common

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: Jesse Pelton
    Created: Thu, 13 May 2004 9:45 AM
       Body:
Does your compiler support C++ namespaces?  Namespaces are designed to address precisely this issue, and Xerces provides tools that you should be able to use to resolve the issue.  See http://xml.apache.org/xerces-c/program-others.html#CPPNamespace.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/XERCESC-1212?page=comments#action_35526

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESC-1212

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESC-1212
    Summary: Xerces-C Conflicts with fdlibm: enum names too common
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Xerces-C++
 Components: 
             Utilities
             Validating Parser (DTD)
             Validating Parser (Schema) (Xerces 1.5 or up only)
   Versions:
             2.5.0

   Assignee: 
   Reporter: Robert Buck

    Created: Thu, 13 May 2004 8:46 AM
    Updated: Thu, 13 May 2004 9:45 AM
Environment: ALL

Description:
For those developers that use the freely distributable math library, or fdlibm, a conflict exists between the definition of UNKNOWN. Specifically, if you include fdlibm headers prior to xerces-c headers, xerces-c user applications will not compile.

Choosing common names such as UNKNOWN is not helpful to those of us that link in many third-party libraries, since the likelihood that a conflict will exist with such a name is greatly increased. Please prefix the names with something that distinguishes the enum value as being from Xerces-C. In the very least, set it as a standard practice in future enum types to use more conspicuous names. It would be nice if you changed these before these names get entrenched in C++ user code.

I do have a work-around, but it's rather ugly. I just raise this to your attention, mostly to suggest the adoption of such a coding practice.

Thanks


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org

[jira] Updated: (XERCESC-1212) Xerces-C Conflicts with fdlibm: enum names too common

Posted by xe...@xml.apache.org.
The following issue has been updated:

    Updater: Alberto Massari (mailto:amassari@progress.com)
       Date: Mon, 4 Oct 2004 3:34 AM
    Changes:
             Component changed to Build
             Component changed from Utilities
             Component changed from Validating Parser (DTD)
             Component changed from Validating Parser (Schema) (Xerces 1.5 or up only)
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/XERCESC-1212?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESC-1212

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESC-1212
    Summary: Xerces-C Conflicts with fdlibm: enum names too common
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Xerces-C++
 Components: 
             Build
   Versions:
             2.5.0

   Assignee: 
   Reporter: Robert Buck

    Created: Thu, 13 May 2004 8:46 AM
    Updated: Mon, 4 Oct 2004 3:34 AM
Environment: ALL

Description:
For those developers that use the freely distributable math library, or fdlibm, a conflict exists between the definition of UNKNOWN. Specifically, if you include fdlibm headers prior to xerces-c headers, xerces-c user applications will not compile.

Choosing common names such as UNKNOWN is not helpful to those of us that link in many third-party libraries, since the likelihood that a conflict will exist with such a name is greatly increased. Please prefix the names with something that distinguishes the enum value as being from Xerces-C. In the very least, set it as a standard practice in future enum types to use more conspicuous names. It would be nice if you changed these before these names get entrenched in C++ user code.

I do have a work-around, but it's rather ugly. I just raise this to your attention, mostly to suggest the adoption of such a coding practice.

Thanks


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org

[jira] Commented: (XERCESC-1212) Xerces-C Conflicts with fdlibm: enum names too common

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: Robert Buck
    Created: Thu, 13 May 2004 10:36 AM
       Body:
I can do that as well, if I can only find on Sun's site where they would take bug reports on fdlibm, and convince them to make the change.

Since fdlibm has a greater install base (at least presently), it would make sense (at least in my own mind) changing it in Xerces-C. Especially since this is actually rather new code in Xerces-C. Whereas, the code in fdlibm is 11 years older than the Xerces-C code. I'm not saying what Sun Microsystems did was all that brilliant - the developers that wrote this ought to have known better than to use something as common as UNKNOWN in a #define. That's just asking for trouble.

But alas, I still would like to request that either (or both) the following occur:

a. establish a prefix convention for enums, perhaps X_ for future code
b. change this particular enum to something other than "UNKNOWN" (please?)

---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/XERCESC-1212?page=comments#action_35529

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESC-1212

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESC-1212
    Summary: Xerces-C Conflicts with fdlibm: enum names too common
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Xerces-C++
 Components: 
             Utilities
             Validating Parser (DTD)
             Validating Parser (Schema) (Xerces 1.5 or up only)
   Versions:
             2.5.0

   Assignee: 
   Reporter: Robert Buck

    Created: Thu, 13 May 2004 8:46 AM
    Updated: Thu, 13 May 2004 10:36 AM
Environment: ALL

Description:
For those developers that use the freely distributable math library, or fdlibm, a conflict exists between the definition of UNKNOWN. Specifically, if you include fdlibm headers prior to xerces-c headers, xerces-c user applications will not compile.

Choosing common names such as UNKNOWN is not helpful to those of us that link in many third-party libraries, since the likelihood that a conflict will exist with such a name is greatly increased. Please prefix the names with something that distinguishes the enum value as being from Xerces-C. In the very least, set it as a standard practice in future enum types to use more conspicuous names. It would be nice if you changed these before these names get entrenched in C++ user code.

I do have a work-around, but it's rather ugly. I just raise this to your attention, mostly to suggest the adoption of such a coding practice.

Thanks


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org

[jira] Commented: (XERCESC-1212) Xerces-C Conflicts with fdlibm: enum names too common

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: Robert Buck
    Created: Thu, 13 May 2004 9:55 AM
       Body:
Yes, but namespaces is not at issue - the C preprocessor is. The issue specifically is that many C libraries use #define. This particular one (fdlibm) does the following:

#define UNKNOWN 5

That is the issue. The only way around this is to change the definition, or change the name of the enum in Xerces. The latter is preferable.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/XERCESC-1212?page=comments#action_35527

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESC-1212

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESC-1212
    Summary: Xerces-C Conflicts with fdlibm: enum names too common
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Xerces-C++
 Components: 
             Utilities
             Validating Parser (DTD)
             Validating Parser (Schema) (Xerces 1.5 or up only)
   Versions:
             2.5.0

   Assignee: 
   Reporter: Robert Buck

    Created: Thu, 13 May 2004 8:46 AM
    Updated: Thu, 13 May 2004 9:55 AM
Environment: ALL

Description:
For those developers that use the freely distributable math library, or fdlibm, a conflict exists between the definition of UNKNOWN. Specifically, if you include fdlibm headers prior to xerces-c headers, xerces-c user applications will not compile.

Choosing common names such as UNKNOWN is not helpful to those of us that link in many third-party libraries, since the likelihood that a conflict will exist with such a name is greatly increased. Please prefix the names with something that distinguishes the enum value as being from Xerces-C. In the very least, set it as a standard practice in future enum types to use more conspicuous names. It would be nice if you changed these before these names get entrenched in C++ user code.

I do have a work-around, but it's rather ugly. I just raise this to your attention, mostly to suggest the adoption of such a coding practice.

Thanks


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org

[jira] Commented: (XERCESC-1212) Xerces-C Conflicts with fdlibm: enum names too common

Posted by ji...@apache.org.
The following comment has been added to this issue:

     Author: David Bertoni
    Created: Thu, 13 May 2004 10:16 AM
       Body:
I hope you've also filed the same request with the developers of that library.  After all, it's that library which is at fault, and UNKNOWN could conflict libraries other than Xerces-C.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/XERCESC-1212?page=comments#action_35528

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESC-1212

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESC-1212
    Summary: Xerces-C Conflicts with fdlibm: enum names too common
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Xerces-C++
 Components: 
             Utilities
             Validating Parser (DTD)
             Validating Parser (Schema) (Xerces 1.5 or up only)
   Versions:
             2.5.0

   Assignee: 
   Reporter: Robert Buck

    Created: Thu, 13 May 2004 8:46 AM
    Updated: Thu, 13 May 2004 10:16 AM
Environment: ALL

Description:
For those developers that use the freely distributable math library, or fdlibm, a conflict exists between the definition of UNKNOWN. Specifically, if you include fdlibm headers prior to xerces-c headers, xerces-c user applications will not compile.

Choosing common names such as UNKNOWN is not helpful to those of us that link in many third-party libraries, since the likelihood that a conflict will exist with such a name is greatly increased. Please prefix the names with something that distinguishes the enum value as being from Xerces-C. In the very least, set it as a standard practice in future enum types to use more conspicuous names. It would be nice if you changed these before these names get entrenched in C++ user code.

I do have a work-around, but it's rather ugly. I just raise this to your attention, mostly to suggest the adoption of such a coding practice.

Thanks


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org