slsh's require breaks jed-extra

John E. Davis davis at space.mit.edu
Thu Jun 7 16:20:13 UTC 2007


On Thu, 7 Jun 2007 16:54:44 +0200, Jörg Sommer <joerg at alea.gnuu.de> said:
>Even if we can fix this, there is another problem: require from slsh
>doesn't care about jed_load_path. While jed-extra uses jed_load_path
>everywhere=E2=80=94it breaks a second time.

  Jed uses an evalfile hook that slang calls when files are loaded.
It is here where jed's load path is used.  So, require does know about
this path, and if not, there is something wrong.  Do you have an
example where this fails?

>But I think we should make an advantage out of this situation and should
>remove jed_library_path. IIRC, this is a long standing task. Right, John?

It is on the TODO list-- perhaps I can work it into the next svn
checkin.  But that should not affect require.

>BTW: John, there's a bug in SLpath_get_load_path. If SLpath_set_load_path
>was not called before the path is NULL and SLang_create_slstring is
>called with NULL.

I don't regard that as a bug.  SLpath_get_load_path returns the value
of the load path, and if it has not been set, the value is NULL.

Thanks,
--John



More information about the Pkg-jed-devel mailing list