>Anything that makes it difficult for me to build an app against the Xerces >source tree or a binary release without code changes, doesn't sound like a >good thing. Would one way to allow folks to take their time moving to the new includes be to set up files with the old names that just include the new ones...? (I don't have a position on the proposal.) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
- Re: Changing include to include/xercesc Jason E. Stewart
- RE: Changing include to include/xercesc Hespelt, Steve (Exchange)
- Re: Changing include to include/xercesc Murray Cumming
- Re: Changing include to include/xercesc Murray Cumming
- Re: Changing include to include/xercesc Tinny Ng
- Re: Changing include to include/xercesc Murray Cumming
- Re: Changing include to include/xercesc Arnaud Le Hors
- RE: Changing include to include/xercesc Arnold, Curt
- Re: Changing include to include/xercesc Murray Cumming
- Re: Changing include to include/xercesc Murray Cumming
- RE: Changing include to include/xercesc Joseph_Kesselman
- RE: Changing include to include/xercesc Herb Chong
- Re: Changing include to include/xercesc Murray Cumming
- Re: Changing include to include/xercesc Arnaud Le Hors
- Re: Changing include to include/xercesc Jason E. Stewart
- Re: Changing include to include/xercesc Murray Cumming
- RE: Changing include to include/xercesc Hespelt, Steve (Exchange)
- RE: Changing include to include/xercesc VAN DYCK Pieter
- Re: Changing include to include/xercesc Jason E. Stewart
- Re: Changing include to include/xercesc Arnaud Le Hors
- Re: Changing include to include/xercesc Jason E. Stewart
