We're not building Xalan against Xerces-C 1.5 yet, since we'll do our next
release with 1.4.  When we move up to Xerces-C, we can rename our class, I
suppose.

A while back, we adopted the policy of preceeding all of our new class
names with Xalan.  The Xerces team should consider doing the same thing, so
we can avoid more conflicts -- especially with common names like
StringTokenizer.

Dave



                                                                                       
                         
                    James Berry                                                        
                         
                    <jberry@critica        To:     Xerces C Dev 
<[EMAIL PROTECTED]>                   
                    lpath.com>             cc:     (bcc: David N Bertoni/CAM/Lotus)    
                         
                                           Subject:     Xerces-C 1.5 & Xalan-C 
StringTokenizer symbols conflict 
                    06/10/2001                                                         
                         
                    08:38 PM                                                           
                         
                    Please respond                                                     
                         
                    to xerces-c-dev                                                    
                         
                                                                                       
                         
                                                                                       
                         



In trying half-heartedly to link the Xerces-C 1.5 candidate up with the
current Xalan-C TOT, I get a symbol conflict: they each use a similar
StringTokenizer class.

Does anybody have a plan for this? Since Xerces is coming late to the party
maybe a change should be made there before 1.5?

Thoughts? Or is somebody way past me on this one?

-jdb
--
/**********************************
 James D. Berry
 mailto:[EMAIL PROTECTED]
 vox:503.265.1213 fax:503.222.3020
 **********************************/



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to