[Openmcl-devel] Coping with a name conflict
Tim Bradshaw
tfb at tfeb.org
Tue Mar 22 01:24:29 PDT 2022
It's nice that globally renaming things is that easy ... or it would be nice if it was, which it's not, of course.
Better to fix the real problem, that the package is wrong, I think.
> On 22 Mar 2022, at 04:50, Andrey G. Grozin <A.G.Grozin at inp.nsk.su> wrote:
>
> On Mon, 21 Mar 2022, Denis Lorrain wrote:
>> - The annoying point is that my dbg macro-function is everywhere in my code, sometimes commented out, but often not. I
>> could change its name, but it would be quite tedious to edit all my source files, written over the last 15 or 20 years...
> Why?
>
> find . -name '*.lisp' | xargs sed -e 's/dbg/something/g' -i
>
> Just a single line.
>
> Andrey
More information about the Openmcl-devel
mailing list