eiffel-edom-developers Mailing List for EDOM
Brought to you by:
colin-adams
Menu
▾
▴
eiffel-edom-developers — Discussion about the development of EDOM.
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(13) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Colin P. A. <co...@co...> - 2003-07-08 14:12:33
|
This version now requires the latest CVS version of xalan-c. -- Colin Paul Adams Preston Lancashire |
|
From: Colin P. A. <co...@co...> - 2003-07-07 14:28:49
|
I have tagged 1.3 in CVS with the tag: rel-1-3. -- Colin Paul Adams Preston Lancashire |
|
From: Colin P. A. <co...@co...> - 2003-06-30 10:08:59
|
The latest code in CVS now requires the use of GOBO 3.2 or later, as it uses the c_compiler_options option to control debugging of the C++ interface layer. -- Colin Paul Adams Preston Lancashire |
|
From: Colin P. A. <co...@co...> - 2003-06-13 22:38:01
|
>>>>> "Mike" == Mike Raschend <ras...@gm...> writes:
Mike> C:\src\ise\EDOM\xslt/xalanc/xslt.h(393) : error C2146:
Mike> syntax error : missing ')' before identifier 'xor'
OK - I guess MSC isn't uptodate with standard C++ syntax. I'll change
it soon.
--
Colin Paul Adams
Preston Lancashire
|
|
From: Mike R. <ras...@gm...> - 2003-06-13 21:20:27
|
C:\src\ise\EDOM\xslt/xalanc/xslt.h(393) : error C2146: syntax error : missing ')' before identifier 'xor' C:\src\ise\EDOM\xslt/xalanc/xslt.h(393) : error C2059: syntax error : ')' C:\src\ise\EDOM\dom/xercesc/dom.h(969) : error C4715: 'xercesc_eiffel_dom_CharacterData::xercesc_data' : not all control paths return a value C:\src\ise\EDOM\dom/xercesc/dom.h(953) : error C4715: 'xercesc_eiffel_dom_CharacterData::xercesc_substring_data' : not all control paths return a value my c++ knowledge isn't so good that I could commit a solution |
|
From: Mike R. <ras...@gm...> - 2003-06-13 16:27:03
|
> > Mike> Yes, but my only little problem is now, that I don't know > Mike> where or how I change the geant-file to call gepp on the > Mike> ge-files. > > I think we need a build.eant file in the EDOM root directory. > This should have one target - install - which should call gepp. can you do this ? > > > >> These changes are checked into CVS, but they won't clash with > >> your changes, so you can just checkin against the main branch. > > I've upgraded you to developer. That should give you check-in rights, > I think. Ok, I must wait some hours before my new ssh-key is active, so this time I send you a zip file with the small changes. |
|
From: Colin P. A. <co...@co...> - 2003-06-13 10:21:19
|
Mike> Yes, but my only little problem is now, that I don't know
Mike> where or how I change the geant-file to call gepp on the
Mike> ge-files.
I think we need a build.eant file in the EDOM root directory.
This should have one target - install - which should call gepp.
>> These changes are checked into CVS, but they won't clash with
>> your changes, so you can just checkin against the main branch.
I've upgraded you to developer. That should give you check-in rights,
I think.
--
Colin Paul Adams
Preston Lancashire
|
|
From: Mike R. <ras...@gm...> - 2003-06-13 09:33:38
|
> > >> > >> Would you like to take on this task? > > Mike> Yes, at the weekend. > > Have you done this? > Yes, but my only little problem is now, that I don't know where or how I change the geant-file to call gepp on the ge-files. > These changes are checked into CVS, but they won't clash with your > changes, so you can just checkin against the main branch. I have no checkin rights. I can sent it via zip-file ? |
|
From: Colin P. A. <co...@co...> - 2003-06-13 08:50:10
|
I'm ready to release 1.2, which should fix all remaining known memory problems. I have implemented reference counting on the C++ bridging object for DOM_DOCUMENT, and I've added a dispose routine for XPATH_XPATHNSRESOLVER. -- Colin Paul Adams Preston Lancashire |
|
From: Colin P. A. <co...@co...> - 2003-06-11 05:15:36
|
>>>>> "Colin" == Colin Paul Adams <co...@co...> writes:
Colin> These changes are checked into CVS, but they won't clash
Colin> with your changes, so you can just checkin against the main
Colin> branch.
Not quite true - index.html has been updated to refer to Pathan 1.2.1,
so do a CVS update before you try updating this.
--
Colin Paul Adams
Preston Lancashire
|
|
From: Colin P. A. <co...@co...> - 2003-06-11 05:10:13
|
>>>>> "Mike" == Mike Raschend <ras...@gm...> writes:
>> The library.xace files we need adjusting to reflect the spec
>> subdirectories.
That was rubbish on my part.
>>
>> Would you like to take on this task?
Mike> Yes, at the weekend.
Have you done this?
I've implemented a reference counting scheme for the C++ Document
wrapper objects. This fixes all known memory problems (but there are
probably more memory leaks associated with XPath processing - I'll
take a look at these before releasing 1.2 - incidentally, Pathan 1.2.1
is out now, and works unchanged with the current CVS).
These changes are checked into CVS, but they won't clash with your
changes, so you can just checkin against the main branch.
--
Colin Paul Adams
Preston Lancashire
|
|
From: Mike R. <ras...@gm...> - 2003-06-03 11:11:42
|
> >>>>> "Colin" == Colin Paul Adams <co...@co...> writes: > > >>>>> "Mike" == Mike Raschend <ras...@gm...> writes: > Mike> I must comment out lines in some source files (this is not > Mike> so good). It is possible to make changes to build edom easy > Mike> without xalan support ? > > Colin> I can't see how to do it. > > Actually, I can now. > > We would have to use gepp. > > Then > > #ifndef USE_XALAN > > #endif > > could be put around the code to be commented out. > > The system.xace file in tests (not in tests/xslt, of course) should be set > to define this > symbol. And the rest of the system.xace file could be conditionally > coded around the symbol. > > Then we would need a geant install task, to run gepp. > > The library.xace files we need adjusting to reflect the spec > subdirectories. > > Would you like to take on this task? Yes, at the weekend. |
|
From: Colin P. A. <co...@co...> - 2003-06-03 10:53:58
|
>>>>> "Colin" == Colin Paul Adams <co...@co...> writes:
>>>>> "Mike" == Mike Raschend <ras...@gm...> writes:
Mike> I must comment out lines in some source files (this is not
Mike> so good). It is possible to make changes to build edom easy
Mike> without xalan support ?
Colin> I can't see how to do it.
Actually, I can now.
We would have to use gepp.
Then
#ifndef USE_XALAN
#endif
could be put around the code to be commented out.
The system.xace file in tests (not in tests/xslt, of course) should be set to define this
symbol. And the rest of the system.xace file could be conditionally
coded around the symbol.
Then we would need a geant install task, to run gepp.
The library.xace files we need adjusting to reflect the spec
subdirectories.
Would you like to take on this task?
--
Colin Paul Adams
Preston Lancashire
|
|
From: Colin P. A. <co...@co...> - 2003-06-03 05:10:35
|
>>>>> "Mike" == Mike Raschend <ras...@gm...> writes:
Mike> I must comment out lines in some source files (this is not
Mike> so good). It is possible to make changes to build edom easy
Mike> without xalan support ?
I can't see how to do it.
Mike> It is a pity that I cant compile
Mike> xalan-c with the borland compiler.
Have you asked on the xalan list?
--
Colin Paul Adams
Preston Lancashire
|
|
From: Mike R. <ras...@gm...> - 2003-06-02 20:14:51
|
Hi Colin ! When I build edom with the borland compiler I must comment out some lines in the xace file (thats ok), and I must comment out lines in some source files (this is not so good). It is possible to make changes to build edom easy without xalan support ? It is a pity that I cant compile xalan-c with the borland compiler. -- MfG MikeR |
|
From: Colin P. A. <co...@co...> - 2003-05-28 09:01:03
|
Xerces-c 2.3.0 has now been released. This includes support for XML 1.1 and XML namespaces 1.1, as well as partial support for DOM document normalisation. But EDOM 1.1 will not link against it. When I have sorted out what changes are needed, I'll prepare a 1.2 release specifically for xerces 2.3.0. -- Colin Paul Adams Preston Lancashire |
|
From: Colin P. A. <co...@co...> - 2003-05-22 13:38:32
|
Hello Mike, I've defined you as a Tester to the project (since that's what you've been doing). I don't know whether or not that gives you CVS write access or not. if you do decide to do any actual development, and find you cannot check in, then I'll change your status to Developer. Since 1.1 was released, I've finally started to get some answers from the Pathan developers. As a result, I've already discovered (and fixed in CVS) one memory leak that can arise from using XPath. If I get answers to my other questions, then I shall do the same. -- Colin Paul Adams Preston Lancashire |
