hi jas and all. On 21 Feb 2002, (Jason E. Stewart) wrote:
> "John Utz" <[EMAIL PROTECTED]> writes: > > > did you check *all* of your work into cvs? i tried to build out of > > cvs today at about 2pm Pacific Standard Time and CVS was still > > looking mighty 1.5.2-ish, so it wont do me any good to not have all > > of it there.... > > Yeah, it was the first commit of the 1.6 stuff, so it has > everything. I hadn't realized that anyone had actually ever checked > out the code from CVS... it's a funny thing. because on some projects, i am deep in the tree, others, i just refuse to have anything to do with unreleased code! for instance, i have been running FreeBSD since before 1.0 (and that's going to be 9 years in october! wow! ) and i have *never* run freebsd-current. but the xerces stuff has been non-stop CVS because XMLSchema support is very new for everybody, and the XMLSchema that i am working with (MPEG7) is huge and it makes very aggressive use of the features therein. > > > http://xml.apache.org/dist/xerces-p/experimental/ > > > > > > I haven't bumped the version number since last time, but it is new. > > > > that's ok, the tarball will be my fallback if i cant build the cvs stuff. > > > > generally, i've been working out of the xml-xerces tree since december for > > both java and c++ because i've been pushing the envelope pretty hard with > > both flavors. > > That's excellent. It's very useful to have people actually developing > code, I hope you'll be able to add your example to the list of sample > apps. that is my intent. > There are almost guaranteed to be features still missing. I am willing > to add things as you need them, but you can do it as well. The trick > is to look into the Xerces.i file (the SWIG interface module) and see > what header files I list after a %include directive. Those are the > files that SWIG is wrapping, if you need a class that is defined in a > header file that I don't currently include, you can just add another > %include (and an #include at the top - those show up in the Xerces.C > %file). Then re-run make, and SWIG should kick in to re-create > Xerces.pm and Xerces.C for you. In order for that to work, however, > you must have run 'perl Makefile.PL' with the XERCES_DEVEL environment > variable set. this is great. now that i have this 1 paragraph tutorial ( where they all that simple :-) ) i will actually try and roll my own instead of being passive and i'll send you the diffs. > If this is too daunting, I can help. i think that the deal is that the first one will be hard and you'll need to talk me thru it, but after that it should make sense. i noted with interest the speed in which you fixed the issue when i raised it yesterday.... > Cheers, > jas. ps: now, what's *really* gonna suck is getting this ported to win32. that is where i have to ultimately run this thing. i am pretty concerned about that because i cant get any answer from the guy that was allegedly porting xerces-c to cygwin. > --------------------------------------------------------------------- > 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]
