Add an example to the manual which explains shows to use the package

[fingolfin]

A section with a full example (or probably multiple), from start to end, would be helpful. Both for profiling and for code coverage. As it is, all the pieces may be documented, but what is missing is a guide that tell you how to put them all together. I think this is cruicial if we want people to actually (be able to) use these great facilities you created.

[olexandr-konovalov]

(+1) This may be useful: http://www.azumanga.org/gap/2015/11/18/gap-line-profiling.html

[fingolfin]

... except that link now is broken and neither http://www.azumanga.org nor https://www.azumanga.org seem to exist... if the explanations were in the manual, everybody would have a copy of them and they couldn't be lost :-(

[fingolfin]

Seems to be here now: http://www.joyofsearch.com/line-by-line-profiling-in-gap.html
See also http://www.joyofsearch.com/line-by-line-code-coverage-gap.html

But if websites go away / move around things w/o leaving redirects etc., we'll loose this again

Those two pages are mostly simple text, converting them to GAPDoc XML shouldn't take more than half an hour. I am busy now, but I might just try it.

[fingolfin]

@ChrisJefferson I just wanted to use the profiling package again. I am sad to say that I rarely do, because it's such a pain to find out again each time how to use it. I really wish those blog posts (which apparently moved again -- or simply are gone, as you started a fresh blog from scratch and deleted all old article ?!?? :-(((( )

[fingolfin]

I created PR #55 to at least partially address this.