{"shas":[["4078d29d83e45a0b059ca5a71877ec36a4174a01","16c132cdb62bf524638d8d0ca9d3a80bc302630c@random-state.net","1.0.46.18: terser C-STRING unparsing\n\n Omit parts with default values from the unparsing: just\n\n  (C-STRING :EXTERNAL-FORMAT :DEFAULT :ELEMENT-TYPE CHARACTER)\n\n becomes C-STRING, and\n\n  (C-STRING :EXTERNAL-FORMAT :UTF-8 :ELEMENT-TYPE CHARACTER)\n\n becomes (C-STRING :EXTERNAL-FORMAT :UTF-8), etc.","Nikodemus Siivola"],["bb3994fcc9a556d1a26d35f6ff9386d01030821d","16c132cdb62bf524638d8d0ca9d3a80bc302630c@random-state.net","1.0.46.19: add :NOT-NULL option to C-STRING type\n\n By default NIL is a valid C-STRING, translated to and from C's NULL. This is\n very convenient because many C functions that normally return strings return\n NULL to indicate \"false\" or \"don't know\" -- and less commonly also special\n case it as an argument.\n\n There are however many C functions that don't check for NULL, so we want a\n non-horrible way to say that NIL is not a good value to pass on...\n\n ...it remains to be seen if this is non-horrible enough, but at least it\n fixes a bunch of memory faults from doing things like (posix-getenv nil), and\n replaces them with type-errors.\n\n Not all C-STRING types have been audited yet, just a bunch of the more\n obvious ones.","Nikodemus Siivola"],["930a0e019b4c823da04d52e907d322a296fb9ae3","16c132cdb62bf524638d8d0ca9d3a80bc302630c@random-state.net","1.0.46.20: better error messages for invalid variables\n\n Based on patch by Roman Marynchak, lp#387333.\n\n * Same code checks for LET and LET* in addition to lambda-lists, so make sure\n   the messages make sense for both contexts. Binding forms converted to\n   LAMBDA -- like MULTIPLE-VALUE-BIND -- still get odd messages for duplicate\n   variable names, though.\n\n * Make the messages for keywords, defined constants, and global lexicals\n   better.","Nikodemus Siivola"],["8e6218a244d65acbae7ff5d3396705a4dec537d9","16c132cdb62bf524638d8d0ca9d3a80bc302630c@random-state.net","1.0.46.21: renaming oops in MAKE-PACKAGE\n\n When WITH-PACKAGES was renamed WITH-PACKAGE-GRAPH, MAKE-PACKAGE was\n not updated -- but amusingly no error was signalled, because\n\n * The form was that of a function call, so no program-error.\n\n * Before the undefined function could be called, a non-local transfer always\n   took control elsewhere, so no undefined-function error.","Nikodemus Siivola"],["17c4e8486b40a6ac1c1dc5094d2e706f4cf229ed","4a078282e49dcb71df915c1cf4a7968e2585bffa","1.0.46.22: fix sb-posix readdir on SunOS/x86\n\n for the time being, disable :largefile on SunOS/x86.  Unfortunately,\n sb-grovel cannot navigate the somewhat sticky way in which struct\n dirent gets setup for a 32-bit host with 64-bit ino_t on SunOS, so\n sb-posix:readdir breaks\n\n :largefile works fine on SunOS x86_64, and will be re-enabled on x86\n after I get some more time to fight with the alien def for struct dirent","jimwise"],["f849f46aa175919bd46a32d9305b1162f9d0d2f5","4a078282e49dcb71df915c1cf4a7968e2585bffa","1.0.46.23: fix an actual random bug in mkstemp test\n\n On some platforms (including Solaris, FWIW), the character \".\"  is one of\n the characters mkstemp can use when filling in an \"XXXXXX\" template.  When\n this (randomly) occurs during the running of this test, PATHNAME-NAME, of\n course breaks on the last such random \".\" character, and the test fails in\n a way which will not repeat until the next time such a character is\n randomly chosen.\n\n Since readdir actually returns a string, break the string on the first \".\"\n explicitly, instead of making a path from the string and calling\n pathname-name.\n\n This will need to be revisited if we add mkstemp support on win32 in the\n future.","jimwise"],["503ad9d8685b335a69dc667dec4ce48f1a03af98","16c132cdb62bf524638d8d0ca9d3a80bc302630c@random-state.net","1.0.46.24: fix MAKE-INSTANCE regression from 1.0.45.19\n\n lp#728650\n\n We cannot use an optimized CTOR if there is an :AROUND method potentially\n supplying initialization arguments via CALL-NEXT-METHOD.\n\n So:\n\n * Add SIMPLE-NEXT-METHOD-CALL slot to STANDARD-METHOD: initialize it to T iff\n   the method doesn't use CALL-NEXT-METHOD at all, or only as\n   (CALL-NEXT-METHOD).\n\n * Allow an optimized CTOR in the presence of INITIALIZE-INSTANCE :AROUND\n   methods iff those methods only contain simple forms of CALL-NEXT-METHOD.","Nikodemus Siivola"],["4c8caa51bca73bd7c454713b93e71879502eb2b2","3498722d6a4b6bdfe34e4bbf4876b880284dd5bc@bobobeach.com","1.0.46.25: consolidate common code from x86-64-darwin-os.c and x86-darwin-os.c into darwin-os.c\n\n * lots of code in x86-64-darwin-os.c and x86-darwin-os.c was\n   duplicated. consolidated into darwin-os.c and wrapped with\n   appropriate #ifdefs.\n\n * darwin-os.c now #includes \"thread.h\" but not \"bsd-os.h\"","Cyrus Harmon"],["e8c80f67856e7fd94f64574d10b5637fef5af1f6","3498722d6a4b6bdfe34e4bbf4876b880284dd5bc@bobobeach.com","1.0.46.26: mach-exception-handler improvement: current_mach_task\n\n * define current_mach_task variable, squirrel away the value of\n   mach_task_self there and use that instead of calling mach_task_self\n   so that we don't leak send rights all over the place","Cyrus Harmon"],["d3af5593ffff1c39a2f8fa8113704803f347e22f","3498722d6a4b6bdfe34e4bbf4876b880284dd5bc@bobobeach.com","1.0.46.27: fix mach port leakage\n\n * store mach_thread_self() results in current_mach_thread and\n   deallocate the mach_port after thread_set_exception_ports call\n\n * fix error messages in lose strings in mach_thread_init\n\n * catch_exception_raise now calls mach_port_deallocate for the\n   exception_port, the thread and the task\n\n * These changes seem to get rid of most of the leaking port\n   rights. However, MachPortDump shows when running the\n   threads.impure.lisp tests, there are still a number of ports that\n   stick around with a single send right.","Cyrus Harmon"],["cbc0ad89d5bb05c1bfa2c712bc8a0e2bbe7b5673","3498722d6a4b6bdfe34e4bbf4876b880284dd5bc@bobobeach.com","1.0.46.28: fix mach port leakage on x86 too\n\n * call mach_port_deallocate on exception_port, thread and task at the\n   end of x86 version of catch_exception_raise","Cyrus Harmon"],["2f7e7231ad6128af80102fa2031f483e00e7a2bc","3498722d6a4b6bdfe34e4bbf4876b880284dd5bc@bobobeach.com","1.0.46.29: fix run-compiler.sh for darwin/x86\n\n * default arch is now x86_64, so check for x86 and use arch i386 if\n   appropriate","Cyrus Harmon"],["fd290d06b69b9754d4bfbf8c845570ff87cb228e","3498722d6a4b6bdfe34e4bbf4876b880284dd5bc@bobobeach.com","1.0.46.30: don't deallocate exception_port and check return values from mach_port_deallocate calls\n\n * mach_port_deallocate of the exception_port was returning\n   KERN_INVALID_RIGHT; assume this call was bogus and remove it.  So\n   now we can be more strict about checking the return values of the\n   other deallocate calls.","Cyrus Harmon"],["2c5a710f4da100f8aa9c7262fa76395f73ee4307","3498722d6a4b6bdfe34e4bbf4876b880284dd5bc@bobobeach.com","1.0.46.31: clean up mach port deallocation on x86\n\n * don't deallocate the exception_port port and check the return\n   values from deallocating the thread and task ports","Cyrus Harmon"],["f2c2f0d480ce63689af4b4d63fa5b51d024641b1","372472441d7c034d4295a8ba27e1c69bec36d14a","1.0.46.32: export sb-kernel::redefinition-with-defmacro\n\n  Export sb-kernel::redefinition-with-defmacro the same way we already\n  export sb-kernel:redefinition-with-defun and it's CLOS friends.","cracauer"],["4d7b7a70cbb3cd7bf64897747d407f40803e3d72","5429250fe07c242264adf0e0267fee16c9a6b935@users.sourceforge.net","1.0.46.33: constraint: Don't substitute REFs when replacement LEAF is not visible.\n\n  * Bug reported by Frank Duncan, additional diagnosis by Heka Treep,\npatch review and revision by Nikodemus Siivola.\n\n  * Introduce LEAF-VISIBLE-FROM-NODE-P, which verifies that the LEAF\nabout to be substituted is visible from the NODE to be modified.\n\n  * Add LEAF-VISIBLE-FROM-NODE-P as an additional precondition to\ncalling CHANGE-REF-LEAF, which does the actual substitution.\n\n  * And, for good measure, added a test to the test suite.","Alastair Bridgewater"],["3c54829dd2c9c654433ef469b320a6e9ff098177","fa58591a66c64a81da50cedb0d601e92d5b751b6@users.sourceforge.net","1.0.46.34: Fix tests for builds without sb-eval.\n\nAdd #+sb-evel to cases which bind sb-ext:*evaluator-mode* to :interpret.","Stas Boukarev"],["b5f1bfd5090893a125ba7520fc2f30ad663b3af9","16c132cdb62bf524638d8d0ca9d3a80bc302630c@random-state.net","1.0.46.35: first cut at MAP-ROOT\n\n Walking references from an arbitrary lisp object.","Nikodemus Siivola"],["9649ba118decaf0b6c7715e9224843d16016ad6b","16c132cdb62bf524638d8d0ca9d3a80bc302630c@random-state.net","1.0.46.36: par for course, committed the wrong version of MAP-ROOT as 1.0.46.35\n\n This one actually works instead of having package errors.","Nikodemus Siivola"],["0a8778552a8499dd4614c9aada7dfca3dfcc6997","16c132cdb62bf524638d8d0ca9d3a80bc302630c@random-state.net","1.0.46.37: SIMPLE-CONDITION slots are initialized with NIL if not supplied\n\n  So says CLHS.\n\n  When there is no format control and *PRINT-ESCAPE* is false,\n  signal an error.","Nikodemus Siivola"]],"repo":"nikodemus/SBCL","actor":"nikodemus","ref":"refs/heads/master","size":61,"head":"bdb254eac36a86f015c9cd7c52c7459029dc3736","actor_gravatar":"5cd0acc03793e7944454dbb533bbfe43","push_id":30857399}