<!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">
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:dherring@tentpost.com">dherring@tentpost.com</a> wrote:
<blockquote
cite="mid:d75b25b9b4cd14d9890e50101c44a87a.squirrel@webmail.tentpost.com"
type="cite">
<pre wrap="">LW wrote</pre>
<pre wrap=""><!---->
IIRC, the Dr. Scheme editor had such features back in 1999. </pre>
</blockquote>
<br>
I have long felt that it's a shame that the Common<br>
Lisp community and the Scheme community are<br>
so badly splt. I strongly suspect that Common<br>
Lisp has a lot to learn from DrScheme.<br>
<br>
<blockquote
cite="mid:d75b25b9b4cd14d9890e50101c44a87a.squirrel@webmail.tentpost.com"
type="cite">
<pre wrap=""> They can be
very useful on occasion; but the need to interact with them can be a
hindrance. Also annoying is when the act of refactoring code breaks the
tools used to simplify the process.
At ILC09, Duane Rettig outlined a smart debugger that could step all the
way from source through macros down to compiled code. A similar framework
may be needed to expose the IT in an anaphoric macro.
</pre>
</blockquote>
Very interesting. It sure would be nice if all that good<br>
work being done at Franz were open source. (I do<br>
understand why it's not.)<br>
<br>
--- Dan<br>
<blockquote
cite="mid:d75b25b9b4cd14d9890e50101c44a87a.squirrel@webmail.tentpost.com"
type="cite">
<pre wrap="">
- Daniel
_______________________________________________
pro mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pro@common-lisp.net">pro@common-lisp.net</a>
<a class="moz-txt-link-freetext" href="http://common-lisp.net/cgi-bin/mailman/listinfo/pro">http://common-lisp.net/cgi-bin/mailman/listinfo/pro</a>
</pre>
</blockquote>
</body>
</html>