Two clarifications I'd like to add to my previous announcement (both of
which were prompted by Zsolt :p ):
1. Some Attribute values take something like (Either Bool String); this
is used when upstream indicates that two different types of values
are allowed. Typically in this kind of
On Jul 19, 2009, at 04:13 , Ivan Lazar Miljenovic wrote:
1. Some Attribute values take something like (Either Bool String);
this
is used when upstream indicates that two different types of values
are allowed. Typically in this kind of situation, the allowed
String
values are limited
2009/7/20 Brandon S. Allbery KF8NH allb...@ece.cmu.edu:
Shouldn't String then be replaced by a sum type? In fact, as described this
would subsume the Either as well.
-- replace Either Bool String: AttrN are the strings, AltValue the bool
data upstreamValue = AttrA | AttrB | AltValue
Yes, as
I am pleased to announce a new release of the graphviz package for
Haskell, which provides bindings to the GraphViz [1] suite of tools.
[1] http://www.graphviz.org/
Probably the biggest and most important change in this release is that
AFAICT, all 152 attributes utilised/supported by GraphViz
Hi,
On Sat, Jul 18, 2009 at 10:23 AM, Ivan Lazar Miljenovic
ivan.miljeno...@gmail.com wrote:
I am pleased to announce a new release of the graphviz package for
Haskell, which provides bindings to the GraphViz [1] suite of tools.
Nice work!
As the way of defining an attribute for a specific
