About RIPE NCC | Contact  | Search | Sitemap    
Homepage RIPE NCC  
RIPE NCC Mail Archives
     
Mailing Lists:
RIPE NCC Navigation Ends
Link to NCC Lists Archive NCC Lists Archive
Link to RIPE Lists Archive RIPE Lists Archive
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

[irrtoolset]Making IRRToolSet compile...

  • From: Glen Turner < >
  • Date: Tue, 10 Feb 2004 15:00:01 +1030
  • Organization: Australian Academic and Research Network

Tony Li wrote:

> prefix.hh:377: parse error before `and'

Because ISO C++ says 'and' is a lexical synonym for '&&'.
You'll need to rename the function (I used 'pand').

> It seems to me that if you want others to help with this project,
> we either need to be a tad more portable in our coding or we
> need to be extremely specific about which tools are approved
> for use.

Hi Katie,

Could I encourage you to port the source code to ISO C++?

I've made a start, and my compiling but segfaulting patches
are at http://www.aarnet.edu.au/~gdt/patch/

I wasn't going to post to the list until they were running,
but I felt I should contribute them now as they make the
case that the move to ISO C++ is simply drudgery (this is
the first time I've used C++, so there can't be any wizard
knowledge required).  There's only a handful of code that
needs rewriting, the same compile errors simply appear many
times.

When I'm finished, would you accept a patch to move the
codebase to ISO C++ (and thus compile under GCC3.2.2)?
I don't particularly want to end up maintaining a fork.

Finally, I notice the code uses the discontinued libg++
(included as source).  Perhaps in the longer term this
could be replaced by the STL (and Boost, if needed)?
  
Regards,
Glen

-- 
Glen Turner         Tel: (08) 8303 3936 or +61 8 8303 3936 
Network Engineer
Australian Academic & Research Network   www.aarnet.edu.au





  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE NCC | Service Announcements | Site Map | LIR Portal | About RIPE | Contact | Legal | Copyright Statement
RIPE NCC Homepage Go to the RIPE NCC LIRPortal Go to the RIPE Community pages