Mailman 3 January 1999 - Cplusplus-sig

Re: [C++-SIG] CXX (Release 8) and EGCS 1.1.1
by Paul F. Dubois Jan. 14, 1999

Jan. 14, 1999

Someone told me they had succeeded with another alteration to the config file, but that the resulting compile times were through the roof. This would indicate ECGS is not good at templates. If so, this is a not-unheard-of state for a C++ compiler. I plan to try ECGS myself at some point. I regret that I lost this message in the process of moving recently. If the person who sent it to me would comment about the change necessary I would appreciate it. -----Original Message----- From: John Barnard <barnard(a)hustat.harvard.edu> To: c++-sig(a)python.org <c++-sig(a)python.org> Date: Wednesday, January 13, 1999 3:43 PM Subject: [C++-SIG] CXX (Release 8) and EGCS 1.1.1 >Has anyone successfully used CXX (Release 8) with EGCS 1.1.1? When I >try to compile any of the examples that are distributed with CXX I get >the following messages: > >gcc -I/home/barnard/lib/include -I/usr/include/python1.5 arraytest.cxx >/home/barnard/lib/include/CXX_Objects.h: In method `class ::Py::seqref<T> ::Py::SeqBase<T>::front()': >In file included from /home/barnard/lib/include/CXX_Array.h:3, > from arraytest.cxx:5: >/home/barnard/lib/include/CXX_Objects.h:923: use of class template `template <class T> ::Py::seqref<T>' as expression >/home/barnard/lib/include/CXX_Objects.h: In method `class ::Py::seqref<T> ::Py::SeqBase<T>::back()': >/home/barnard/lib/include/CXX_Objects.h:931: use of class template `template <class T> ::Py::seqref<T>' as expression >/home/barnard/lib/include/CXX_Objects.h: In method `int ::Py::String::capacity() const': >/home/barnard/lib/include/CXX_Objects.h:1229: confused by earlier errors, bailing out >make: *** [all] Error 1 > >I'm not sure if the problem is with the template mechanism or the >namespace mechanism (everything that's supposed to be under the std >namespace is in the global namespace for the libstdc++ distributed >with EGCS 1.1.1). Turning off namespace support in CXX doesn't help. > >I'm running Red Hat 5.2 (2.0.36) on a Pentium II. > >Thanks, > >John Barnard >Assistant Professor >Department of Statistics >Harvard University >Phone: (617) 495-1603 >Fax: (617) 496-8057 >Email: barnard(a)stat.harvard.edu > >_______________________________________________ >C++-SIG maillist - C++-SIG(a)python.org >http://www.python.org/mailman/listinfo/c++-sig > >

1 0

CXX (Release 8) and EGCS 1.1.1
by John Barnard Jan. 13, 1999

Jan. 13, 1999

Has anyone successfully used CXX (Release 8) with EGCS 1.1.1? When I try to compile any of the examples that are distributed with CXX I get the following messages: gcc -I/home/barnard/lib/include -I/usr/include/python1.5 arraytest.cxx /home/barnard/lib/include/CXX_Objects.h: In method `class ::Py::seqref<T> ::Py::SeqBase<T>::front()': In file included from /home/barnard/lib/include/CXX_Array.h:3, from arraytest.cxx:5: /home/barnard/lib/include/CXX_Objects.h:923: use of class template `template <class T> ::Py::seqref<T>' as expression /home/barnard/lib/include/CXX_Objects.h: In method `class ::Py::seqref<T> ::Py::SeqBase<T>::back()': /home/barnard/lib/include/CXX_Objects.h:931: use of class template `template <class T> ::Py::seqref<T>' as expression /home/barnard/lib/include/CXX_Objects.h: In method `int ::Py::String::capacity() const': /home/barnard/lib/include/CXX_Objects.h:1229: confused by earlier errors, bailing out make: *** [all] Error 1 I'm not sure if the problem is with the template mechanism or the namespace mechanism (everything that's supposed to be under the std namespace is in the global namespace for the libstdc++ distributed with EGCS 1.1.1). Turning off namespace support in CXX doesn't help. I'm running Red Hat 5.2 (2.0.36) on a Pentium II. Thanks, John Barnard Assistant Professor Department of Statistics Harvard University Phone: (617) 495-1603 Fax: (617) 496-8057 Email: barnard(a)stat.harvard.edu

1 0

Re: your mail
by Paul F. Dubois Jan. 7, 1999

Jan. 7, 1999

In re the changes to CXX in release 8, I had noticed that in 1.5.2 there were some new members in the type tables. I didn't track how far back that change went -- 1.5, 1.5.1, ?. But if it doesn't compile you can just kill the new members as I'm not using them for anything yet as I haven't had time to figure them out. As to the comment someone posted about the release 8 Windows installer not wanting to work with 1.5.1, this is because it is supposed to set a registry key based on the Python version. Maybe I'm not doing something right. If you don't have the key that matches your Python then the python path is screwed up. I'm in the process of moving my office so please forgive the slow responses. -----Original Message----- From: David Ascher <da(a)skivs.ski.org> To: Christopher J. Phoenix <cphoenix(a)best.com> Cc: Paul F. Dubois <dubois1(a)llnl.gov> Date: Tuesday, January 05, 1999 1:41 PM Subject: Re: your mail > >On Tue, 5 Jan 1999, Christopher J. Phoenix wrote: > >> Using Visual C++ 5.0 to build the CXX directory of NumPy release 8 (Dec. 28): >> >> r.cxx >> Include\CXX_Objects.h(923) : error C2665: 'seqref::seqref' : none of the 2 >> overloads can convert parameter 1 from type 'class Py::SeqBase<class >> Py::Char> *const ' >> Include\CXX_Objects.h(931) : error C2665: 'seqref::seqref' : none of the 2 >> overloads can convert parameter 1 from type 'class Py::SeqBase<class >> Py::Char> *const ' >> >> I followed these instructions: >> c:\wherever> python makethis.py >> c:\wherever> msdev workspace.dsw >> [Go to "Build", pull down "Batch Build", do "Build All", exit DevStudio] >> >> seqref<T> back() { >> return seqref(this, size()-1); // line 923 >> } >> >> I'm a bit confused; seqref is a template, so >> seqref (SeqBase<T>& seq, int j) >> : s(seq), offset(j), the_item (s.getItem(j)){} >> should be able to create any Py::SeqBase<whatever>, right? Or is it the >> Py:: that's confusing it? > >I have no idea -- I haven't tried to build r8 yet. > >> Also, the release notes for 8 say that the type table was changed to conform >> to Python 1.5.2. Does that mean it won't work with 1.5.1? > >I hope not. Paul, any ideas? > >--david > >

1 0