RE: [boost] Re: Graph broken for vc7.1 after 1.31?
Hi again, I still can't compile the graph library after the last change on the 29:th of Sept. Strangely I see regression tests been run on vc7.1 since then and I wonder how that could be possible? http://www.meta-comm.com/engineering/boost-regression/developer/graph.html Regards, Christian -----Original Message----- From: Christian Wahlgren on behalf of Christian Wahlgren Sent: Thu 2004-09-30 09:06 To: boost@lists.boost.org Cc: Subject: RE: [boost] Re: Graph broken for vc7.1 after 1.31? Hi, Perhaps my fault - It wasn't that easy to just define YY_NO_UNISTD_H to make graph compile with vc7.1. The problem is that two non-ANSI C functions is called: b->yy_is_interactive = file ? (isatty( fileno(file) ) > 0) : 0; A little documentation search on Win32 gives: <io.h> int _isatty(int); <stdio.h> int _fileno(FILE*); As for how to solve these non-portable stuff with perhaps some BOOST defines, I think you all know better than I do. Kindest Regards, Christian -----Original Message----- From: Doug Gregor [mailto:dgregor@cs.indiana.edu] Sent: Wed 2004-09-29 17:45 To: boost@lists.boost.org Cc: Subject: Re: [boost] Re: Graph broken for vc7.1 after 1.31? On Sep 29, 2004, at 9:25 AM, Vladimir Prus wrote:
Were you able to check it on VC 7.1?
No. I'd appreciate if you could try there.
I'll try to do so later.
We'll deprecate it in 1.32.0 (when, hopefully, we will have a new GraphViz parser that works well) and remove it afterwards.
How the new parser will be implemented?
Spirit.
Is it written yet? Would be interesting to see.
I think the parser is written but the semantic actions are not, so it isn't functional yet. We're trying to unify on some kind of system for dynamic properties, so that we can deal with reading in arbitrary vertex/node attributes. I have a GraphML parser that handles dynamic properties, which hopefully will also work well in the new GraphViz parser. If I get some time post-1.32.0 (hah!), we'll try to get all those bits in.
Granted, they've dropped support for older, broken compilers, so someone will still be getting hurt by this.
Right. OTOH, I start to wonder if BGL should drop support for old compilers as well. (borland and vc6 are marked unusable already). There seem to be a lot of workaround inside BGL which means even reading the code hard.
We promised to keep the parts of the BGL needed for the Python lib in working order. But I've marked borland and vc6 unusable because they've never really been usable and are a huge maintenance burden. Doug _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Hi Christian,
I still can't compile the graph library after the last change on the 29:th of Sept.
I've removed the calls to 'isatty', let me know if it works now.
Strangely I see regression tests been run on vc7.1 since then and I wonder how that could be possible?
http://www.meta-comm.com/engineering/boost-regression/developer/graph.html
Because the regression tests do not build the graphviz parser? - Volodya
On Oct 5, 2004, at 4:09 AM, Christian Wahlgren wrote:
Hi again,
I still can't compile the graph library after the last change on the 29:th of Sept.
You're referring to the GraphViz parser, I assume? That's the only part of the the graph library that needs to be compiled separately. If you don't need the GraphViz parser, you don't need to build the library. Getting the code that flex/bison spews out to compile on all of our target platforms has turned out to be a nightmare. I'll try to get it working, but no guarantees.
Strangely I see regression tests been run on vc7.1 since then and I wonder how that could be possible?
http://www.meta-comm.com/engineering/boost-regression/developer/ graph.html
There are no tests for the GraphViz parser, and there won't ever be because this parser is going to disappear as soon as we get any replacement. Horrible, horrible, horrible. Doug
participants (3)
-
Christian Wahlgren -
Doug Gregor -
Vladimir Prus