<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV>All:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>There has been some debate among the researchers about which CL to use for this project. Although I have experience with both SBCL and Allegro, it would appear that Allegro is not going to release their 8.0 evaluation version anytime soon and this is the only version that includes the asdf: functionality we will be using to maintain and install builds of cl-semantic.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Yes asdf can be easily added to Allegro, but SBCL is very easy to setup, and in a project where are are attempting to get as many developers interested as possible, many whom may not have university access to Allegro, it seems important that we have a CL that is ready right out of the box (we may even group all the source for Wilber and other necessary requires in to one .gz for easy deployment in to each developer's repository).</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>However, from my experience using SLIME with Allegro and SBCL, SBCL is extremely slow and is generally buggy on OSX do to Apple's Crash Reporter actively looking for Mach exceptions because Mac OSX has no idea that a program can do a SIGSEGV and keep on living.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Anyone have any suggestions?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I would also like suggestions on a GUI environment for cl-semantic, perhaps ltk (uses Tk).</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Also, please start posting directly to the message group instead of to individual email addresses so that we can leverage our new home at common-lisp.net. We have had many people joint the development and announce list and we owe it to them to let everyone know what is going on, even if they have yet to join the project.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Thanks!</DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV>Brandon Werner</DIV><DIV>cl-semantic project administrator</DIV><DIV><FONT class="Apple-style-span" color="#121212" face="Arial"></FONT></DIV><DIV><A href="http://common-lisp.net/project/cl-semantic/">http://common-lisp.net/project/cl-semantic/</A></DIV><DIV><A href="mailto:brandon.werner@mac.com">brandon.werner@mac.com</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-style-span">cl-semanic is<SPAN class="Apple-converted-space"> </SPAN><FONT class="Apple-style-span" face="Arial"><SPAN class="Apple-style-span" style="font-family: Arial; ">a</SPAN></FONT><FONT class="Apple-style-span" face="Arial"><FONT class="Apple-style-span" color="#000000"><SPAN class="Apple-style-span" style="font-family: Arial; "> collection of RDF/OWL extraction and relationship parsing macros written in Common Lisp.</SPAN></FONT></FONT></SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR class="Apple-interchange-newline"></SPAN> </DIV><BR></BODY></HTML>