However the Myst III Exile will NOT start up on my Intel Mac Quadcore Nehalem
The downloaded Myst Application and carbon libray claim they are A PowerPC application.
=============================================================
Can not open the program “Myst3 OS X US”
since PowerPc-programs are no longer supported:
=============================================================

Cheers: Max!

#!/bin/sh

# Colors
red=`echo “33[91m"`
green=`echo "33[92m"`
yellow=`echo "33[93m"`
blue=`echo "33[94m"`
purple=`echo "33[95m"`
cyan=`echo "33[96m"`

# Bold colors
bold=`echo "33[1m"`
bold_red=`echo "33[1;91m"`
bold_green=`echo "33[1;92m"`
bold_yellow=`echo "33[1;93m"`
bold_blue=`echo "33[1;94m"`
bold_purple=`echo "33[1;95m"`
bold_cyan=`echo "33[1;96m"`

# Color reset
reset=`echo "33[0m"`

# Patterns
double_colon="s/::/$red&$reset/;"
rocket="s/=>/$red&$reset/;"
left_arrow="s//$red&$reset/;"
strings="s/\"[^\"]*\”/$yellow&$reset/g;”
chars=”s/’[a-zA-Z]*’/$purple&$reset/g;”

exec “`which ghc`” –interactive ${1+”$@”} |\
sed “$double_colon
$rocket
$right_arrow
$left_arrow
$strings
$chars”

You could really take this pretty far and style all sorts of things. Numbers however can get a bit dicey since the color codes contain numbers.

Though this feels a bit hackish, it works well enough for me.

For JSON grammars it might actually be a feature: you can map two different JSON constructs to the same Haskell value, and on the way back consistenly map the Haskell value to the preferred of the two JSON constructs.

Btw, I fixed the missing <>s in your comment.

iso1, iso2 :: Iso Char ()
iso1 = unstack (unit . inverse (lit ‘x’))
iso2 = unstack (unit . inverse (lit ‘y’))

In isolation, these partial isomorphisms are fine. But (iso1 <> iso2) has a problem: It is not really inverse to (inverse (iso1 <> iso2)).

> convert (iso1 <> iso2) ‘y’
Just ()

> convert (inverse (iso1 <> iso2)) ()
Just ‘x’.

Oups. We successfully converted from Char to () and back to Char, but we arrived at a different character. I am not sure how serios that problem is in your setting.

From a theoretical point of view, I believe this problem is fundamental with partial isomorphisms: They do not really support choice. That is why in our paper, we used partial isomorphisms only for semantic actions, and built the additional layer of syntax descriptions on top of it.

> The <> is just another name for mappend from Data.Monoid

Can you make it be from Edward Kmett’s semigroups package instead? Otherwise, your module will be less convenient to use with any program that uses a datatype which is a semigroup but not a monoid. Now that I noticed the semigroups package, I am finding more and more of those…