<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Is the build to which Denis refers different from the CL 1.12 download on Github? <div class="">And if so is it generally available?<div class="">(The link <span style="font-family: "courier new", courier, monaco, monospace, sans-serif; font-size: 16px;" class=""><a href="http://setf.clozure.com/~rme/ccl-1.12.1-ide-big-sur.zip" class="">http://setf.clozure.com/~rme/ccl-1.12.1-ide-big-sur.zip</a> </span>is broken.)</div><div class="">Thanks,</div><div class="">Martin<br class=""><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 21, 2022, at 5:00 PM, Denis Lorrain <<a href="mailto:dlo_lorrain@yahoo.fr" class="">dlo_lorrain@yahoo.fr</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div class="ydp2224ebd2yahoo-style-wrap" style="font-family:courier new, courier, monaco, monospace, sans-serif;font-size:16px;"><div class=""><div class="">Hello all,<br class=""></div><div class=""><br class=""></div><div class="">- Having updated from macOS 11.6.3 to 12.3, I had to change from the old AppStore CCL 1.11.7 to CCL 1.12.1.</div><div class="">- R. Matthew Emerson kindly gave me this last build:</div><div class=""> <a href="http://setf.clozure.com/~rme/ccl-1.12.1-ide-big-sur.zip" class="">http://setf.clozure.com/~rme/ccl-1.12.1-ide-big-sur.zip</a></div><div class="">- Happily, CCL 1.12.1 runs seemingly very well with macOS 12.3, whereas CCL 1.11.7 was very problematic with macOS 11.6.3. So I'm globally very satisfied with both changes.</div><div class=""><br class=""></div><div dir="ltr" data-setdir="false" class="">- Unfortunately CCL 1.12.1 now introduces a name conflict with my own code, which did not occur before. Briefly summarized:</div><div class=""><br class=""></div><div class="">===========================================================</div><div class="">Clozure Common Lisp Version 1.12.1 (v1.12.1-3-g2ae800e1) DarwinX8664</div><div class="">For more information about CCL, please see <a href="http://ccl.clozure.com" class="">http://ccl.clozure.com</a>.</div><div class="">CCL is free software. It is distributed under the terms of the Apache</div><div class="">Licence, Version 2.0.</div><div class="">? (function DBG)</div><div class="">#<Compiled-function DBG #x30000015DD1F></div><div class="">? *package*</div><div class="">#<Package "CCL"></div><div class="">? (find-symbol "DBG")</div><div class="">DBG</div><div class="">:INTERNAL</div><div class="">? (defmacro dbg (forme &optional fonction)</div><div class=""> (if fonction</div><div class=""> `(format *standard-output* "~4Tdbg-> ~S : ~S = ~S~%"</div><div class=""> (quote ,fonction) (quote ,forme) ,forme)</div><div class=""> `(format *standard-output* "~4Tdbg-> ~S = ~S~%" (quote ,forme) ,forme)))</div><div class="">; Warning: The function DBG is being redefined as a macro.<br class=""></div><div class="">; While executing: (SETF MACRO-FUNCTION), in process Listener(4).</div><div class="">DBG</div><div class="">? (dbg a) => crash: AltConsole</div><div class=""> Lisp Breakpoint</div><div class=""> ? for help</div><div dir="ltr" data-setdir="false" class=""> [nnnn] Clozure CL kernel debugger:</div><div dir="ltr" data-setdir="false" class=""><span class="">===========================================================</span><br class=""></div><div dir="ltr" data-setdir="false" class=""><span class=""><br class=""></span></div><div dir="ltr" data-setdir="false" class="">- The conflict is created by my definition of dbg as a macro-function. You understand it's a simple developing help, inserted for debugging, checking things on the fly, printing internal values, etc.</div><div class=""><br class=""></div><div class="">- 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...</div><div class=""><br class=""></div><div dir="ltr" data-setdir="false" class="">=> Is there some package trick which could solve this name conflict? So called shadowing? Unfortunately, my knowledge about packages doesn't extend further than the clumsy demo above.</div><div class="">=> Could anyone suggest a hopefully simple solution?</div><div class=""><br class=""></div><div class="">Sorry for this long message. Many thanks in advance,</div><div dir="ltr" data-setdir="false" class=""><br class=""></div></div><div dir="ltr" data-setdir="false" class=""> DLO</div><div class="ydp2224ebd2signature"><div style="font-family:courier, monaco, monospace, sans-serif;font-size:13px;" class=""><div class="">--</div><div class="">Denis Lorrain</div><div class=""><a href="http://denislorrain.org/" rel="nofollow" target="_blank" class="">http://www.denislorrain.org</a></div><div dir="ltr" class="">Recordings of selected piano works:</div><div dir="ltr" class=""> <a href="https://soundcloud.com/user-205054622" rel="nofollow" target="_blank" class="">http://w</a><a href="http://orks.denislorrain.org" class="">orks.denislorrain.org</a></div><div dir="ltr" class=""><a href="mailto:dlo@denislorrain.org" class="">e-mail: dlo@denislorrain.org</a></div><div class="">--</div></div></div></div></div></div></blockquote></div><br class=""></div></div></div></body></html>