good evening;
On 2010-04-15, at 03:04 , Robert Goldman wrote:
One of my own systems got blown up by ASDF-OUTPUT-TRANSLATIONS
recently,
and the case may be an interesting one:
[ ... ]
We have a pont-file which ISA cl-source-file.
But there is no .lisp file to begin with. Instead, we have
One of my own systems got blown up by ASDF-OUTPUT-TRANSLATIONS recently,
and the case may be an interesting one:
I am working on a system that involves taking an ontology from the
Protege tool, and interpreting it as CL.
So we have a special component type which is pont (from Protege ontology).
To prevent Lisp files from being redirected, you can add a rule such as
((:root #p**/*.lisp) t)
in your translations.
OR, you can make sure your output-file methods return T as a second
value to prevent relocation.
[ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ]
On 4/14/10 Apr 14 -8:52 PM, Robert Goldman wrote:
On 4/14/10 Apr 14 -8:41 PM, Faré wrote:
To prevent Lisp files from being redirected, you can add a rule such as
((:root #p**/*.lisp) t)
in your translations.
OR, you can make sure your output-file methods return T as a second
value to
False alarm. A-B-L compatibility /is/ working here.
Now I need to figure out /why/ it is working for compatibility, but
fails when the compatibility is turned off (and the .lisp file gets
written in the wrong place).
Anyway, I clearly shouldn't go messing about with this until I'm sure I
know
