Boost logo

Boost :

From: Christian Wahlgren (christian.wahlgren_at_[hidden])
Date: 2004-10-05 04:09:19

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?


-----Original Message-----
From: Christian Wahlgren on behalf of Christian Wahlgren
Sent: Thu 2004-09-30 09:06
To: boost_at_[hidden]
Subject: RE: [boost] Re: Graph broken for vc7.1 after 1.31?

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:

  int _isatty(int);

  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,

-----Original Message-----
From: Doug Gregor [mailto:dgregor_at_[hidden]]
Sent: Wed 2004-09-29 17:45
To: boost_at_[hidden]
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.


Unsubscribe & other changes:

Boost list run by bdawes at, gregod at, cpdaniel at, john at