Malcolm Wallace wrote:
In fact, my wish as a library author would be: please tell me what
you, as a beginner to this library, would like to do with it when you
first pick it up? Then perhaps I could write a tutorial that answers
the questions people actually ask, and tells them how to get the
I think a few examples can go a long way.
I remembered seeing a lot of requests for examples in the results, so I went
back and skimmed the spreadsheet. I found that 11 of the 34 responses under
Library Documentation explicitly called out examples as desirable.
Combined with Heinrich's
Stephen Tetley wrote:
Replying to someone's compliant in the first section:
Malcolm Wallace and Colin Runciman's ICFP99 paper functioned well as a
tutorial for HaXml when I used it - maybe it is a bit out of date now?
HaXml is hardly a dire case.
... for the right audience. I guess the point
On 09/12/11 17:48, Stephen Tetley wrote:
Replying to someone's compliant in the first section:
Malcolm Wallace and Colin Runciman's ICFP99 paper functioned well as a
tutorial for HaXml when I used it - maybe it is a bit out of date now?
HaXml is hardly a dire case.
The paper is out-of-date,
On 13 Sep 2011, at 18:59, Michael Orlitzky wrote:
Malcolm Wallace and Colin Runciman's ICFP99 paper functioned well as a
tutorial for HaXml when I used it - maybe it is a bit out of date now?
HaXml is hardly a dire case.
The paper is out-of-date, so it's worse than useless: you'll waste
On 09/13/2011 05:15 PM, Malcolm Wallace wrote:
I am the first to admit that HaXml's documentation is not as good as
it could be, and I am sorry that you have had a bad experience.
Sorry for the tirade =) That was a while ago, but I definitely felt some
sympathy for the guy in the quote.
On Sep 13, 2011, at 7:38 PM, Michael Orlitzky wrote:
One thing I am puzzled about, is just how extremely difficult it must
be, to click on Detailed documentation of the HaXml APIs from the
HaXml homepage, look for a moment until you see
Text.XML.HaXml.Parse in the list of modules, click on
I would appreciate is a few paragraphs in the toplevel haddock page or
module that describe the general architecture and layout of the
modules, as well as the typical entry points. Since the module system
doesn't have a notion of private modules and it's common to re-export
symbols, it can be
Replying to someone's compliant in the first section:
Malcolm Wallace and Colin Runciman's ICFP99 paper functioned well as a
tutorial for HaXml when I used it - maybe it is a bit out of date now?
HaXml is hardly a dire case.
___
Haskell-Cafe mailing
