On 29 Mar 2014, at 20:07, Stelian Ionescu wrote:
> On Sat, 2014-03-29 at 19:59 +0100, Pascal Costanza wrote:
> [...]
>>>>> That's not how it works, unless you include a bit for *rdff* in the
>>>>> name of the fasl cache directory — and since the plannin
ing the utterer owns
> the domain at stake. Otherwise, why should YOU not be the one to leave
> when we disagree what "love it" means?
I believe you are reading too much into what I wrote. I prefer the defaults of
the CL implementation of my choice not to be overridden by some tool whose
primary purpose is something unrelated to those defaults. That’s all.
Pascal
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.
encountered libraries that don’t load with current ASDF
>> versions anymore, although they are defined as ASDF libraries, which is a
>> shame!
>>
> Sorry, you don't get to complain unless (1) you issue a bug report,
> and (2) the bug isn't fixed by whichever party actually has a bug,
> whether it's the library or ASDF.
I’m not complaining, I’m just mentioning.
Pascal
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.
with current ASDF versions
anymore, although they are defined as ASDF libraries, which is a shame!
Personally, I am maintaining Closer to MOP, and because of that, I can afford
not paying attention to newer ASDF/quicklisp versions only to a limited extent.
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.
If asdf provides a simple and well documented way of disabling a default
directory, the it can be any name. Then it can be ensured that future users are
happy, and at the same time, current setups are unaffected.
Pascal
Sent from my iPad
On 13 Mar 2014, at 08:34, Attila Lendvai wrote:
>> I *
Sent from my iPad
> On 12 Mar 2014, at 23:39, Faré wrote:
>
>> On Wed, Mar 12, 2014 at 6:07 PM, Pascal Costanza wrote:
>> Can I set CL_SOURCE_REGISTRY to a value that deactivates all "default"
>> paths? Then I don't care what the default is...
Can I set CL_SOURCE_REGISTRY to a value that deactivates all "default" paths?
Then I don't care what the default is...
Pascal
Sent from my iPad
On 12 Mar 2014, at 22:14, Faré wrote:
: Faré
>>> : p-cos
>> : rpgoldman
>
>>> asdf is not a tool for beginners. Beginners will either deal with
>>> ~/common-lisp/ is slightly more pretentious, but probably works, too.
> That would be my preference.
>
>>> ~/cl/ is taking a lot of familiarity, and maybe I should keep it my
>>> personal configuration rather than a recommended default.
>>
>> These last two have been rejected by Pascal and
Yuck...
Sent from my iPad
> On 12 Mar 2014, at 18:41, Dave Cooper wrote:
>
>
> On Wed, Mar 12, 2014 at 1:04 PM, Faré wrote:
>
>
>> 1- I think we should proceed and add a default path anyway.
>> ~/cl/ and/or ~/common-lisp/ sound fine to me, and I've seen no one
>> complain about that.
>>
asdf is not a tool for beginners. Beginners will either deal with a bare Common
Lisp implementation, or they want to experiment with third-party libraries, in
which case they want to use quicklisp these days. Once you need to define your
own systems, you're not a beginner anymore, and a good tut
ad
> On 12 Mar 2014, at 08:04, Faré wrote:
>
>> On Wed, Mar 12, 2014 at 2:49 AM, Pascal Costanza wrote:
>> This has the potential of messing up already existing configurations
>> (again!). The choice of ~/lisp would certainly mess up mine, and I can
>> imagine many ot
This has the potential of messing up already existing configurations (again!).
The choice of ~/lisp would certainly mess up mine, and I can imagine many other
scenarios. Please don't do that.
Thanks,
Pascal
Sent from my iPad
> On 12 Mar 2014, at 04:44, "Robert P. Goldman" wrote:
>
> Faré wro
advise against turning warnings into cerror or error. It just
prevents working code from continuing to work, which is gratuitous IMHO.
Pascal
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.
On 24 Jan 2014, at 19:56, Robert P. Goldman wrote:
> Pascal Costanza wrote:
>>
>>> The new ASDF will break systems that subclass OPERATION. Those
>>> libraries' maintainers will have to look at their code, based on the
>>> error message, and see what
> The new ASDF will break systems that subclass OPERATION. Those
> libraries' maintainers will have to look at their code, based on the
> error message, and see what needs to be done. For the vast majority of
> them, five minutes work will suffice. For those that take more... well,
> as you po
superclass, and providing a new
‘new-operation class (or some such) that user code has to use instead.
(new-operation could be a subclass of operation…)
Pascal
--
Pascal Costanza
On 17 Jan 2014, at 18:42, Robert P. Goldman wrote:
> Pascal Costanza wrote:
>>>> If you want to implement checks on subclasses, it’s better to do this in
>>>> initialize-instance / reinitialize-instance on metaclasses, but this
>>>> requires that th
[Sorry for the delay, but I haven’t seen this email before.]
On 13 Jan 2014, at 17:25, Robert P. Goldman wrote:
> Pascal Costanza wrote:
>>> I need to look into a means to identify these problematic cases. Ugh.
>>>> MOP not standardized. Ugh ugh ugh ugh. I
s subclasses is an interface like any other,
and yes, interface changes may have negative consequences. That’s correct for
any kind of interfaces. It can be better to create new interfaces and leave the
existing ones untouched if backwards compatibility is a major concern.
Just my 0.02€…
Pascal
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.
+1
For those who want a strict handling of both cases, they can always set
*break-on-signals* accordingly. (The other way around, switching from a strict
error to to something to ignore, is less convenient.)
Pascal
P.S.: Please don’t over-engineer this. People will not spend a lot of time
thinking about what exactly happens when what part of their version numbers
change how. We need to make the barriers for contributing libraries to the Lisp
community lower, not higher.
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.
Just to chime in in the middle: There is no known solution to the so-called
"DLL hell" problem. Libraries interact badly because of their interactions, not
because one or the other is "bad." Even with the best of intentions, a library
author cannot predict what changes will break existing client
> On 18 Nov 2013, at 16:45, Faré wrote:
>
> On Mon, Nov 18, 2013 at 10:21 AM, Pascal Costanza wrote:
>>> ASDF is not going to hard code an
>>> exception for your library.
>>
>> Closer to MOP already existed before asdf imposed anything on version
>
> On 18 Nov 2013, at 15:54, Faré wrote:
>
>> On Mon, Nov 18, 2013 at 2:34 AM, Pascal Costanza wrote:
>> The 0.xy versions of Closer to MOP were not based on semantic versioning,
>> but on an ad hoc versioning scheme. 1.0.0 did not change any API at all, so
>>
The 0.xy versions of Closer to MOP were not based on semantic versioning, but
on an ad hoc versioning scheme. 1.0.0 did not change any API at all, so is
definitely compatible with the last 0.xy versions. 1.0.0 is supposed to
acknowledge the maturity of the library, that's it.
The FAQ section a
> Moptilities is only on example, there are other libraries
> affected by this problem.
>
> So, my question is: how :depends-on ((:version ...))
> should work, and is the change in the behavior intentional?
>
> Best regards,
> - Anton
>
>
>
>
>
>
>
--
Pascal Costanza
Could you please distinguish between stable and unstable releases. It's fine to
ask the CL community to help with finding and fixing bugs, but there are
situations where this can be a real showstopper, especially when working
against deadlines. You have been very aggressive in the past at pushin
On 5 Oct 2013, at 15:41, Zach Beane wrote:
> Pascal Costanza writes:
>
>> OK, found it. Apparently, you cannot use "~" in ASDF configurations
>> anymore.
>
> ~ syntax has never worked in CMUCL pathnames before. Did it start
> working in 20e?
I guess no
OK, found it. Apparently, you cannot use "~" in ASDF configurations anymore.
Sigh…
Pascal
On 5 Oct 2013, at 12:30, Pascal Costanza wrote:
> Hi,
>
> I just installed CMUCL 20e on my Mac OS X 10.8.5. CMUCL 20e release notes say
> that it comes with ASDF 3.0.2.
>
&
ALL-FUNCTION ERROR
"Invalid pathname ~S: ~*~?"
#P"~/lisp/develop/"
:WANT-ABSOLUTE ...)
Source:
; File: modules:asdf/asdf.lisp
; File has been modified since compilation:
; modules:asdf/asdf.lisp
u're
>> going to break something for someone, but that's none of my business".
>>
>> Anton leans for the latter.
>>
>> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
>> http://fare.tunes.org
>> One can be so anxious to put his &qu
On 6 Feb 2013, at 20:36, Faré wrote:
> On Wed, Feb 6, 2013 at 8:16 PM, Pascal Costanza wrote:
>> Just a question for understanding this better: CLOS provides clean ways to
>> update methods with newer versions. Why do you use fmakunbound instead? Is
>> this to stay
;> /Users/rpg/.cache/common-lisp/acl-8.2-macosx-x64/Users/rpg/circa/code/csm/musliner-tools.fasl
>> ; Fast loading
>> ;
>> /Users/rpg/.cache/common-lisp/acl-8.2-macosx-x64/Users/rpg/circa/code/csm/stochastic.fasl
>>
>> Or -- oh, wait! Did the recompilation of ASDF kille
On 18 Apr 2012, at 15:39, Robert Goldman wrote:
> On 4/18/12 Apr 18 -12:10 AM, Pascal Costanza wrote:
>> On 17 Apr 2012, at 21:36, Robert Goldman wrote:
>>
>>> I am willing to run the ASDF tests using RMCL, since my Mac still has
>>> Snow Leopard, instead of L
y features that
should be in all CL implementations are the ones that are stable and mature!
The situation before ASDF 2.x, when ASDF was not bundled with CL
implementations, was much better!
Pascal
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.
Sent from my iPad
On 17 Apr 2012, at 21:36, Robert Goldman wrote:
> I am willing to run the ASDF tests using RMCL, since my Mac still has
> Snow Leopard, instead of Lion.
>
> *However*, as a non-RMCL user, I have no idea how to run it from the
> shell, so that we can run the test suite on RMC
ixed, and the rest are only latin1 or such in
>>> comments. Bugs filed for all the other systems (but no response so
>>> far).
>>>
>>> IOW, I believe we're mostly arguing about a non-issue.
>>>
>>> —♯ƒ
On 11 Apr 2012, at 17:59, Faré wrote:
> (Misclicked and the message was sent before it was finished. Grrr.)
>
> On Wed, Apr 11, 2012 at 09:02, Pascal Costanza wrote:
>> I'd like to get an idea what the current plans for RMCL are, if any. Since
>> the switch to OS X
On 11 Apr 2012, at 17:48, Robert Goldman wrote:
> On 4/11/12 Apr 11 -8:02 AM, Pascal Costanza wrote:
>> Hi,
>>
>> I'd like to get an idea what the current plans for RMCL are, if any. Since
>> the
>> switch to OS X 10.7, there is no default support f
and go
for the Unix-like names that the ASDF maintainers seem to strongly prefer. RMCL
would be the only Common Lisp implementation that would cause a problem in this
regard.
So, what's the verdict?
Thanks a lot for any hints!
Best,
Pascal
--
Pascal Costanza
The views expressed in this
On 1 Nov 2011, at 23:28, Robert Goldman wrote:
> On 11/1/11 Nov 1 -3:24 PM, Pascal Costanza wrote:
>> Hi,
>>
>> There is a problem in the function directory-files (at least for LispWorks).
>> Currently it is defined like this:
>>
>> (defun* directory-fi
ic)
(pathname-version f))
:name (pathname-name f) :type (pathname-type f))
…or something similar.
There is also a redundant 'u in the 'and form in
filter-logical-directory-results.
Best,
Pascal
--
Pascal Costanza
_
On 13 Jun 2011, at 06:29, Faré wrote:
> On 12 June 2011 11:49, Pascal Costanza wrote:
>> Hi,
>>
>> This is all very frustrating. With ASDF 1.x, everything worked fine and I
>> have never encountered any issues. Since CL implementations "upgraded" to
>&
On 12 Jun 2011, at 17:42, Faré wrote:
> If you think you must fix the spec and all implementations — good luck.
I have had very good and very positive experiences in that regard, as part of
my work on Closer to MOP. Thank you very much.
Pascal
--
Pascal Costanza
The views expressed in t
giant portrait of our Great
> Leader
> - Comrade, do you think the same as I do? inquires the first one, with
> a sincere gaze pleeing into his colleagues' eyes.
> - Comrade, the second one replies and returns the same gaze: yes, I do.
> - In that case, comrade, you're under
t a problem in practice, and
> will keep things somewhat sane.
I'm not sure if I understand all the implications of this change, so I'm
hesitating to applaud this. I don't think it should be ASDF's job to fix this
particular problem.
Pascal
--
Pascal Costanza
The views
On 11 Jun 2011, at 18:47, Nikodemus Siivola wrote:
> On 11 June 2011 19:41, Pascal Costanza wrote:
>
>> Just the one in faslcache. If I ask for that particular file directly
>> (foo:bar;quux.fasl), it will only find the first one and cannot find the
>> second one, so
gt;
> /home/foo/faslcache/bar/quux.fasl
> /home/foo/bar/quux.fasl
>
> should
>
> (directory "foo:bar;x.fasl")
>
> return both, or just the one in faslcache?
Just the one in faslcache. If I ask for that particular file directly
(foo:bar;quux.fasl), it will o
me/type
> (pathname-type one) (pathname-type two)))
> (host (pathname-host one)))
> (mapcar (lambda (d)
>(make-pathname :host host :name name :type type
> :version version :directory d))
> (intersect-directo
e
> you add another translation rule for each physical pathname that
> doesn't fit the logical-pathname portability restrictions.
I haven't used those systems in quite a while, so yes, they may or may not
work. (I think I did some light testing with those systems, but they are not a
pr
On 10 Jun 2011, at 23:00, Nikodemus Siivola wrote:
> On 10 June 2011 23:48, Pascal Costanza wrote:
>
>> * (asdf:load-system :closer-mop)
>>
>> debugger invoked on a ASDF:MISSING-COMPONENT: Component "closer-mop" not
>> found
>
> I can't
well. (I haven't been able to load any
system anymore, but I haven't tried all that I have installed.)
What information do you need from me to be able to fix this?
Best,
Pascal
--
Pascal Costanza
The views expressed in this email are my own, an
On 29 May 2011, at 23:05, Robert Goldman wrote:
> On 5/28/11 May 28 -1:50 PM, Pascal Costanza wrote:
>>
>
>
>> Well, as a minimum, I have two requests to make changes in the documentation:
>>
>> - In Section 3.1, the documentation says the following: &q
CL systems that may not have a notion of a home directory
>> either, however unlikely this may be.)
>>
> When such a new CL system appears, if ever, we can amend ASDF. It's
> not like ASDF is currently devoid of reader conditionals. I had to
nce to ANSI CL will support logical pathnames, and so it will be
relatively straightforward to use logical pathnames in conjunction with ASDF 2,
while ASDF 2 will probably need patching in order to support such a future
Common Lisp system, which can be regarded as
it. (This would make ASDF more robust for potential future CL
systems that may not have a notion of a home directory either, however unlikely
this may be.)
Pascal
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.
__
-style environments, but then getting that
overhead just for wanting to use ASDF doesn't make that much sense. In my
opinion, this speaks for separating them out of ASDF (and ASDF could take
advantage of them in case it detects they are present).
I know this is all difficult to set up an
On 19 May 2011, at 22:13, Robert Goldman wrote:
> On 5/19/11 May 19 -2:57 PM, Faré wrote:
>>>> : Pascal Costanza
>>>> Because ASDF 2.x caused me some trouble in RMCL, I actually put some effort
>>>> into learning logical pathnames - and they seem to work ex
On 19 May 2011, at 21:57, Faré wrote:
>>> : Pascal Costanza
>>> Because ASDF 2.x caused me some trouble in RMCL, I actually put some effort
>>> into learning logical pathnames - and they seem to work extremely well,
>>> as far as I can tell
>>>
On 19 May 2011, at 20:58, Robert Goldman wrote:
> On 5/19/11 May 19 -1:24 PM, Pascal Costanza wrote:
>>
>> On 18 May 2011, at 15:28, Robert Goldman wrote:
>>
>>> On 5/18/11 May 18 -12:26 AM, Chun Tian (binghe) wrote:
>>>> I found a workaroun
e, for example, this may not be the last time in history that the
notion of a user directory isn't supported or, as another example, that
pathnames look different from the usual Unix flavors that you see these days.
Pascal
--
Pascal Costanza
The views expressed in this email are my own, an
On 25 Jan 2011, at 18:57, Robert Goldman wrote:
> On 1/25/11 Jan 25 -7:30 AM, Pascal Costanza wrote:
>>
>> On 23 Jan 2011, at 15:27, Pascal Costanza wrote:
>>
>>> Hi,
>>>
>>> I have encountered two more issues when trying to use ASDF 2 with log
On 23 Jan 2011, at 15:27, Pascal Costanza wrote:
> Hi,
>
> I have encountered two more issues when trying to use ASDF 2 with logical
> pathnames in Allegro and clisp. I have the following logical pathname
> translations in Allegro and clisp respectively:
>
> #+all
On 23 Jan 2011, at 15:33, Zach Beane wrote:
> Pascal Costanza writes:
>
>> I have not defined any ASDF output translations of my own, but I'm
>> using quicklisp, which probably does this.
>
> Quicklisp does not set up ASDF output translations.
Ah, ok, good
ied with ASDF output translations. (In CMUCL,
Clozure, ECL, LispWorks, RMCL, and SBCL, similar logical pathname translations
work as expected.)
I have not defined any ASDF output translations of my own, but I'm using
quicklisp, which probably does this.
Please let me know if I can do someth
On 23 Jan 2011, at 01:50, Pascal Costanza wrote:
>
> On 22 Jan 2011, at 22:05, Faré wrote:
>
>> 2011/1/22 Pascal Costanza :
>>> The reason why I'm having problems is probably because I want to create a
>>> setup that works the same for all the Common Li
On 22 Jan 2011, at 22:05, Faré wrote:
> 2011/1/22 Pascal Costanza :
>> The reason why I'm having problems is probably because I want to create a
>> setup that works the same for all the Common Lisp implementations that I'm
>> using. (I'm the maintainer
me *)
> #P"Snow Leopard:Users:binghe:Lisp:RMCL 5.2.1:"
>
> Seems everything is fine on my side ...
>
> --binghe
>
> 在 2011-1-21，18:29， Pascal Costanza 写道：
>
>> Hi,
>>
>> Thanks a lot to Chun Tian (binghe) and you already!!!
>>
>> Ho
On 21 Jan 2011, at 15:17, Faré wrote:
> On 21 January 2011 05:31, Pascal Costanza wrote:
>> I guess this is going to be a nice exercise in writing portable programs...
>> ;)
>>
> Not for me :-/
>
>>> 1 > (truename (user-homedir-pathname))
>
I guess this is going to be a nice exercise in writing portable programs... ;)
Pascal
On 21 Jan 2011, at 11:29, Pascal Costanza wrote:
> Hi,
>
> Thanks a lot to Chun Tian (binghe) and you already!!!
>
> However, it looks like this is going to be a lot more work:
>
> - A
orkaround, that would be great.
>
> [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
> The rule is perfect: in all matters of opinion our adversaries are insane.
> — Mark Twain
--
Pascal Costanza, mailto:p...@p-
On 20 Jan 2011, at 14:26, Faré wrote:
> On 20 January 2011 06:49, Pascal Costanza wrote:
>> It seems that ASDF 2.x doesn't work with RMCL (ASDF 1.x did). Is that a
>> known issue?
>>
> What is RMCL? Digitool's MCL? It might very well have bitrotten,
> si
Hi,
It seems that ASDF 2.x doesn't work with RMCL (ASDF 1.x did). Is that a known
issue?
Best,
Pascal
--
Pascal Costanza, mailto:p...@p-cos.net, http://p-cos.net
Vrije Universiteit Brussel
Software Languages Lab
Pleinlaan 2, B-1050 Brussel, Be
72 matches
Mail list logo
