[Openmcl-devel] *initial-process* and *current-process*

Arthur Cater arthur.cater at ucd.ie
Fri Jun 24 01:16:53 PDT 2011

Just a guess: Could it be that the variables in question are set by def-load-pointers or similar?

On 24 Jun 2011, at 08:43, Gabriel Dos Reis wrote:

> On Thu, Jun 23, 2011 at 8:26 PM, Gary Byers <gb at clozure.com> wrote:
> [...]
>> The set of per-thread bindings (STANDARD-INITIAL-BINDINGS) may change from
>> release to release; changes that involve public variables should be (and
>> generally have been) documented.
>> The general model of how dynamic bindings work hasn't changed in a
>> very long time (CCL has never really implemented another model), and
>> this model is likely to be either very similar to in most respects or
>> identical to that used in other implementations in its observable
>> behavior.  The set of things that're automatically thread-local is
>> probably larger in CCL than in other implementations and there may be
>> a stronger relationship between the bindings in effect in the creating
>> thread and those established in the created thread in other
>> implementations than there is in CCL.  (In CCL, there's essentially no
>> such relationship.)
> In concrete terms:
>  1.  I installed CCL-1.6 in a separate directory (/tmp/ccl-1.6/), which its
>       script driver  /tmp/ccl-1.6/ccl.
>  2. I checked out the 1.4.x branch of OpenAxiom:
>      svn co https://open-axiom.svn.sf.net/svnroot/open-axiom/1.4.x oa.svn
>  3. I configured OpenAxiom with CCL-1.6
>       mkdir oa.build    ## sibling to oa.svn
>       cd oa.build
>        ../oa.svn/configure --with-lisp=/tmp/ccl-1.6/ccl
>        ## lot of configure outputs
>        make all-boot   ## finishes normally
>     b. I configure afresh OpenAxiom with CCL trunk like above but with
>             --with-lisp=/tmp/ccl.svn/ccl
>         make all-boot  ## fails.
> I've looked at all the possibilities.  The symptoms are as I described
> before: SAVE-APPLICATION only saves the "prior state" of the global
> special variables, not the values they have at the time of SAVE-APPLICATION
> (as does CCL-1.6.)
> This is on an x86-64 running openSUSE-11.3 (I doubt the linux brand matters).
> Are you able to reproduce the success with CCL-1.6 and the failure with
> CCL-trunk?
> -- Gaby
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel

More information about the Openmcl-devel mailing list