To answer my own question, one work-around (not a convenient one)
is to list parameters multiple times after the format string in such
a way that the desired params appear in the right order.
On Tue, Apr 15, 2014 at 11:42 PM, Dominick Samperi
It seems that hsc2hs behaves differently under Windows (when compared with Linux), causing build problems.
An example foo.hsc is attached, along with the foo.hs that is generated using hsc2hs under Windows.
Note the expressions my_$s in the result. It appears that under Windows the %n$s POSIX printf notation is not recognized. The correctly generated file that is produced under Linux is also attached, in foo-linux.hs. Note that proper substitution happens here.
Is there a work-around for this Windows issue?
Thanks, Dominick