On May 25, 2009, at 2:35 PM, Michele Simionato wrote:

I agree that the point of auto-caching is having it enabled by default. My experience with Ypsilon is not significant, but Python does auto- caching
too and in 7 years of use it gave me very little trouble.

That's reassuring.  Doesn't python store the .pyc files in the same
directory as the .py file (the same way ikarus currently does it)?

I remember a couple of
situations where a did remove a .py library and put it in another directory, but forgot to remove the .pyc file, and then my script was importing the wrong ..pyc. However it was not difficult to find out the problem and to solve it.

This would not be a problem in Ikarus (yet) since we locate the source
*before* we locate the cached compiled copy.

In Ypsilon it would be even easier, since all the compiled files and in their
own directory and when in doubt one could just clear the directory.

True.  Though, I would rather it works without doubt. :-)

BTW, since I am at it, is there an Ikarus function returning the
full pathname of a given library? Something like (get-pathname
'(my-lib sub-lib)) ?

The information is there, but not exported.  I will have to make it
(as well as a bunch of other stuff) available as part of the Geiser/ Emacs
integration.  (I just need to get emacs running again first)

Aziz,,,

Reply via email to