{"push_id":2322450575,"size":1,"distinct_size":1,"ref":"refs/heads/utf8-everywhere","head":"2607361f8e32215b17a050a5aa5f89534d50761a","before":"9c9854679edac6ecdc15545603ffc8ad0cf036ba","commits":[{"sha":"2607361f8e32215b17a050a5aa5f89534d50761a","author":{"name":"Brian Dickens","email":"a65c6e78dc3f50f9f27981507e78fe0d6e0c9073@gmail.com"},"message":"Eliminate Debug_Fmt(), replace with rebPrint() API\n\nOne of the premises of Rebol was not to depend on standard library\nfunctions like printf.  However, there was a routine very much like\nprintf written in the C code, which had some adaptations to let it\nprint out Rebol values/series.\n\nDespite its name, it was included in release builds as well.  It\nprovided the string output and formatting for tracing routines that\nusers might be interested in using, and which should be going through\nwhatever I/O methods their console uses.\n\nRen-C compromises on the use of printf() by allowing it in debug\nbuilds.  This makes it possible to instrument Rebol during early boot\nmoments (or otherwise malfunctioning systems) without going through\nany PORT! or print machinery.  However, release builds do not link in\nprintf(), which avoids carrying around code that isn't exposed to\nuserspace (and shouldn't be).\n\nThe debug-build-only usages of Debug_Fmt have been changed to usages\nof printf() and the polymorphic PROBE().  This takes the next step\nand makes all the release-build usages switch over to using rebPrint().\n\n!!! This does not actually test the tracing uses, because tracing was\nbroken.  That will be addressed in a separate commit--this just adds\nthe rebPrint() function, which works.","distinct":true,"url":"https://api.github.com/repos/hostilefork/rebol/commits/2607361f8e32215b17a050a5aa5f89534d50761a"}]}
{"actor":{"display_login":"hostilefork"}}