1 new commit in XEmacs: https://bitbucket.org/xemacs/xemacs/commits/eec2a31de9d6/ Changeset: eec2a31de9d6 User: kehoea Date: 2017-04-21 23:23:36+00:00 Summary: Accept a vector PACKAGE in intern_string() too, thank you Raymond Toy. src/ChangeLog addition: 2017-04-21 Aidan Kehoe <kehoea(a)parhasard.net&gt; * elhash.c (intern_istring): Accept a vector PACKAGE here too, thank you for the bug report, Raymond Toy. Affected #: 2 files diff -r 513b2ed98e3ea153c0e65bce5a93994c48d10b42 -r eec2a31de9d67f78b606314136ed13abb364046d src/ChangeLog --- a/src/ChangeLog +++ b/src/ChangeLog ＠＠ -1,3 +1,9 ＠＠ +2017-04-21 Aidan Kehoe <kehoea(a)parhasard.net&gt; + + * elhash.c (intern_istring): + Accept a vector PACKAGE here too, thank you for the bug report, + Raymond Toy. + 2017-04-19 Aidan Kehoe <kehoea(a)parhasard.net&gt; * buffer.c: diff -r 513b2ed98e3ea153c0e65bce5a93994c48d10b42 -r eec2a31de9d67f78b606314136ed13abb364046d src/elhash.c --- a/src/elhash.c +++ b/src/elhash.c ＠＠ -1862,6 +1862,20 ＠＠ Lisp_Hash_Table *ht; htentry *entries, *probe; + /* Sigh, the poor old GNUs people went ahead and used + binding-obarray-dynamically-and-then-calling-#'read as a way to implement + a cache. I will send them a patch to avoid this, to, for example, write a + hash table object as a readable hash table object, but for the moment we + need to put up with it. */ + if (VECTORP (package)) + { + return call2 (Qxemacs_intern_in_vector, + /* call2() GCPROs the newly-heap-allocated string, that's + not an issue. */ + STRINGP (reloc) ? reloc : make_string (str, len), + package); + } + lookup = oblookup (package, str, len); if (FIXNUMP (lookup)) { Repository URL: https://bitbucket.org/xemacs/xemacs/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email.