[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gcl-devel] asdf

From: Faré
Subject: Re: [Gcl-devel] asdf
Date: Thu, 21 Nov 2013 19:07:24 -0500

When I read the list below, I see than the issue of random only
accepting 32-bit arguments is missing. I'll have to dig through our
archive to find if there aren't more issues missing. Is there another
official bug tracker for GCL? Do you want me to file formal bugs? A
quick Google search finds http://savannah.gnu.org/bugs/?group=gcl but
it doesn't look like it's actively used.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
The older I grow, the more I distrust the familiar doctrine that age
brings wisdom.  — H.L. Mencken

On Thu, Nov 21, 2013 at 6:29 PM, Faré <address@hidden> wrote:
> Ping?
> We're almost there — I'd like to delay the release of ASDF 3.1.1 until
> it works perfectly with GCL (and hopefully gets shipped with GCL via
> (require "asdf")); do you think we can achieve that this month?
> Also, is there a way with GCL to combine several fasls into one? Maybe
> by linking the .o's together? Is there a function to do that? If so, I
> could enable asdf/bundle for GCL.
> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
> (map()(lambda(n l)(princ(subseq (format nil "(~{~A~^
> ~})~%"(let(r)(do-external-symbols(x :cl)(push x r))(sort r #'string<
> :key #'string))) n (+ n l)))(finish-output))'(875 949 8 6010 4863 371
> 11)'(4 3 5 5 3 2 2))
> On Mon, Nov 18, 2013 at 2:45 PM, Faré <address@hidden> wrote:
>>> On the contrary, you've always been very helpful and persistent in your
>>> reports -- thanks!  I admit to having become intimidated by what
>>> appeared as the complexity of this project, and always had other fires
>>> to put out which appeared more pressing ....
>> Thanks for your appreciation. Yes, ASDF is a complex beast,
>> but it's nothing compared to GCL in general,
>> and thanks to you, we're making it a little bit simpler.
>> I'm glad you're overcome the big fires — congratulations.
>> * Another GCL compiler bug:
>> when I changed the definition of getcwd from
>> (let ((*default-pathname-defaults* #p"")) (truename #p""))
>> to
>> (let ((*default-pathname-defaults* *nil-pathname*)) (truename 
>> *nil-pathname*))
>> to guard against e.g. a logical-pathname context while loading asdf
>> and parsing #p"",
>> calls to getcwd result in a segfault.
>> * An another bug: gcl refuses dynamic-extent declaration on functions.
>> uiop/stream.lisp:         #-gcl (declare (dynamic-extent ,@(when
>> before `(#',beforef)) ,@(when after `(#',afterf))))
>> Issue I assume you're working on:
>> * (typep p 'logical-pathname) should be T if p has a logical-pathname host.
>> Previous issues you haven't acknowledged:
>> * apropos is case-sensitive and returns a same symbol many times
>> * compile-file fails to return proper secondary values in case of
>> non-style WARNING.
>> * (pathname-directory #p"foo/") is incorrectly ("foo") instead of
>> (:RELATIVE "foo")
>> I've removed a few #-gcl statements in some tests. I'll run them
>> again, but I suspect they will fail because of the compile-file issue
>> above.
>> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• 
>> http://fare.tunes.org
>> Blaming the prince of the fools should not blind anyone to the vast
>> confederacy of fools that made him their prince.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]