<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
I prefer darcs, as well, actually.<BR>
<BR>
On Thu, 2006-11-16 at 09:34 -0500, Ian Eslick wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">I've used SVN a fair bit although I find managing branches in SVN to be</FONT>
<FONT COLOR="#000000">quite annoying. I prefer darcs, actually, but am happy to use</FONT>
<FONT COLOR="#000000">Subversion - any other elephant users want to chime in on this?</FONT>
<FONT COLOR="#000000">Here's a set of Trac issues for UCW for example. </FONT>
<FONT COLOR="#000000"><A HREF="http://trac.common-lisp.net/ucw/report/1">http://trac.common-lisp.net/ucw/report/1</A> </FONT>
<FONT COLOR="#000000">There's also a WIKI to keep the TODO file and DESIGN file contents live</FONT>
<FONT COLOR="#000000">instead of hiding in the source tree. I'm all for switching to Trac</FONT>
<FONT COLOR="#000000">sooner rather than later.</FONT>
<FONT COLOR="#000000">Google has also put together a nice environment for hosting, but I think</FONT>
<FONT COLOR="#000000">common-lisp.net is where folks go looking for lisp code. 0.6.1 is</FONT>
<FONT COLOR="#000000">probably a few weeks away (although with x86 mac & parallels I can test</FONT>
<FONT COLOR="#000000">all the lisp+os variations locally now; that should speed up the</FONT>
<FONT COLOR="#000000">debugging cycle as I can reproduce anything except 64-bit problems</FONT>
<FONT COLOR="#000000">locally - I think Marco and I resolved that)</FONT>
<FONT COLOR="#000000">Unicode:</FONT>
<FONT COLOR="#000000">By the way, I'm just cleaning up the last of my unicode updates. I kept</FONT>
<FONT COLOR="#000000">having problems with the efficiency hacks in the current support for</FONT>
<FONT COLOR="#000000">Unicode -- there was no canonical representation of strings in the</FONT>
<FONT COLOR="#000000">database; each lisp+machine coded it differently. Also, even though</FONT>
<FONT COLOR="#000000">most strings have codes in the ASCII or Latin-1 character set, SBCL was</FONT>
<FONT COLOR="#000000">still storing 32-bit characters. It now uses the smallest coding size</FONT>
<FONT COLOR="#000000">(8,16 or 32) necessary to represent the string. Support for 8 or 16 is</FONT>
<FONT COLOR="#000000">fairly efficient but if you use unicode code pages > 0 there will be a</FONT>
<FONT COLOR="#000000">performance and storage hit. I put in a convention in where all 16/32</FONT>
<FONT COLOR="#000000">bit unicode strings are stored little-endian (x86 is a little-endian</FONT>
<FONT COLOR="#000000">machine) so I can use native string reader functions to pull shorts and</FONT>
<FONT COLOR="#000000">ints out of the byte vectors when possible. This should greatly compact</FONT>
<FONT COLOR="#000000">string storage on most unicode supporting systems (2x on allegro, 4x on</FONT>
<FONT COLOR="#000000">SBCL).</FONT>
<FONT COLOR="#000000">More string efficiency hacks coming your way soon...</FONT>
<FONT COLOR="#000000">Cheers,</FONT>
<FONT COLOR="#000000">Ian</FONT>
<FONT COLOR="#000000">Robert L. Read wrote:</FONT>
<FONT COLOR="#000000">> Yes.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> I think we should probably do this. I am not experienced with</FONT>
<FONT COLOR="#000000">> subversion, and know nothing</FONT>
<FONT COLOR="#000000">> about Trac, but using a mailing list for everything is a concept we</FONT>
<FONT COLOR="#000000">> need to outgrow.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> On Thu, 2006-11-16 at 07:59 +0100, Pierre THIERRY wrote:</FONT>
<FONT COLOR="#000000">>> If I ain't mistaken, currently Elephant only has a CVS, and no bug</FONT>
<FONT COLOR="#000000">>> tracker of any sort.</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>> Before or after 0.6.1, could you consider switching to subversion and</FONT>
<FONT COLOR="#000000">>> trac, as they are provided by common-list.net? It could help possible</FONT>
<FONT COLOR="#000000">>> contributors to see what remains to be done (comments and attached</FONT>
<FONT COLOR="#000000">>> patches to issues, assignments, etc.).</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>> Curiously,</FONT>
<FONT COLOR="#000000">>> Nowhere man</FONT>
<FONT COLOR="#000000">>> _______________________________________________</FONT>
<FONT COLOR="#000000">>> elephant-devel site list</FONT>
<FONT COLOR="#000000">>> <A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A> <mailto:<A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A>></FONT>
<FONT COLOR="#000000">>> <A HREF="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</A></FONT>
<FONT COLOR="#000000">>> </FONT>
<FONT COLOR="#000000">> ------------------------------------------------------------------------</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> _______________________________________________</FONT>
<FONT COLOR="#000000">> elephant-devel site list</FONT>
<FONT COLOR="#000000">> <A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A></FONT>
<FONT COLOR="#000000">> <A HREF="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</A></FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">elephant-devel site list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A></FONT>
<FONT COLOR="#000000"><A HREF="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</A></FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>