[plt-scheme] questions about profiling & DrScheme startup

Matthew Flatt writes:
 > See the docs for "errortrace" for profiling in MzScheme.

Aha!  Thanks.  I see there's code coverage there, too.  I wish there
were a better way to find out about this kind of stuff than searching
in help-desk.  (I probably wouldn't have thought to search for
"coverage", but now that I see it's there I'm thinking of using it.)
One first step might be to generate an annotated index of the doc.txt
files, i.e. have a sentence or two summary for each rather than just
the list of collection names.  It would also be great to have the
doc.txt files browsable (and searchable) online rather than only being
available in help-desk.  Or are they already somewhere I don't know about?
http://download.plt-scheme.org/doc/ might be a good place to put them.

 > If you include an empty path in your PLTCOLLECTS definition, it is
 > replaced with the default paths. For example,
 > 
 >   :~mflatt/collects
 > 
 > under Unix would add "~mflatt/collects" after the default collection
 > directories.

Thanks.  This would be a good thing to mention in Chapter 16 of the
MzScheme manual.

 > > 3. Is there a place to put arbitrary start-up code for DrScheme?
 > 
 > No. 
 > 
 > For a longer answer, see
 > 
 >  http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&safe=off&frame=right&th=3a0a62b7a2353d7c&seekm=770d8f1a.0112141906.4b840f35%40posting.google.com#link4

I guess what I really wanted was a place to put code that should be
run every time I hit the "Execute" button, not just when DrScheme
starts up.  (I don't really buy the .gccrc comparison-- I'm not
creating an executable, just running my code inside the development
environment.)  But I see that creating a language is probably the
right way to do this.  And for those playing along at home, a more
complete and up-to-date description of how to this is:
http://download.plt-scheme.org/doc/207/html/tools/tools-Z-H-2.html#node_sec_2.1.1

--dougo at place.org