<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I hadn't thought of that.&nbsp; In my case, my embedded documentation serves
a similar purpose.<br>
<br>
Just, before releasing a library, once the interface is solidly
designed and documented I want to change the "provide all defined" to
not include the "%" names, so that I'm not polluting namespaces of
library users.<br>
<br>
<br>
Jay McCarthy wrote at 07/27/2009 07:42 AM:
<blockquote
cite="mid:f66775c40907270442o67c98179qb410266b00edc8dd@mail.gmail.com"
type="cite">
<pre wrap="">I like having to write them out because I'm forced to think about each
function, its interface description, and its contract.

I'm sure that this sort of thing would be a fairly straight-forward
PLaneT tool that leveraged Check Syntax.

Jay

On Mon, Jul 27, 2009 at 5:39 AM, Neil Van Dyke<a class="moz-txt-link-rfc2396E" href="mailto:neil@neilvandyke.org">&lt;neil@neilvandyke.org&gt;</a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Here's a DrScheme feature that I could really use: &nbsp;a command that would add
to the "provide" form of the module in the editor any names defined in the
module but not exported currently, *except* those with names beginning with
the character "%".

A somewhat less-ideal feature would include "%" symbols as well, and I could
just manually delete those.

"%" is a convention that I stole from (I believe) Olin Shivers for marking
names internal to the library. &nbsp;A feature like I described could support
that convention in a generalized way by permitting the user to use regexps
to specify which names to exclude.