Re: [PATCH] Let (format) used in exceptions be overriden

> On 20 Oct 2018, at 21:36, Mark H Weaver wrote: >> replace uses of (format) by (exception-format). > > What's the rationale for this proposed change? > > ... Hi Mark, I don't know how that just ended on guile-devel. It's part of a patch series I sent last year and I don't remember repost

Re: [PATCH] Let (format) used in exceptions be overriden

Hi Daniel, daniel.llor...@bluewin.ch writes: > From: Daniel Llorens > > * module/ice-9/boot-9.scm (exception-format): new variable. Globally > replace uses of (format) by (exception-format). What's the rationale for this proposed change? All but one of the occurrences of 'format' that you re

[PATCH] Let (format) used in exceptions be overriden

/ice-9/boot-9.scm b/module/ice-9/boot-9.scm index 802ca7735..b4d91c350 100644 --- a/module/ice-9/boot-9.scm +++ b/module/ice-9/boot-9.scm @@ -340,6 +340,10 @@ a-cont (define format simple-format) +;; let format used in exceptions be overriden. + +(define exception-format simple-format

[PATCH 2/2] Let (format) used in exceptions be overriden

/ice-9/boot-9.scm b/module/ice-9/boot-9.scm index 802ca7735..7a7a25e88 100644 --- a/module/ice-9/boot-9.scm +++ b/module/ice-9/boot-9.scm @@ -340,6 +340,10 @@ a-cont (define format simple-format) +;; let format used in exceptions be overriden. + +(define exception-format simple-format

Re: Prototype for C++-compatible Guile Exceptions.

ing. > In general, the approach would be to add language-specific wrappers > for all public libguile API functions. These would arrange for Guile > exceptions thrown within libguile to be converted into whatever type > of exception or error handling is desired by the caller. > > ..

Re: Prototype for C++-compatible Guile Exceptions.

Taahir Ahmed writes: > Currently, the use of libguile functions from C++ is fraught with > danger. C++ destructors are not triggered by guile exceptions, and the > dynwind mechanism is ill-suited for application to C++ data structures > (in particular, STL structures). I agree tha

Re: Prototype for C++-compatible Guile Exceptions.

On Tuesday 14 July 2015 13:07:26 you wrote: > I'm posting these patches to feel out the likelihood of this approach to > C++ exception compatibility ever getting adopted into Guile. I just wanted to ping the list to check whether C++ exception compatibility is something desired, and if it is, whet

[PATCH 3/3] Implement Guile exceptions with C++ exceptions.

eh-jmp.{h,cc} contain setjmp/longjmp analogues that use C++ exceptions to unwind the stack. This means that C++ destructors will be called properly in when a guile exception passes through a user code frame. Flow control to resume a continuation remains implemented with setjmp/longjmp, since it

Prototype for C++-compatible Guile Exceptions.

ilure. -- Currently, the use of libguile functions from C++ is fraught with danger. C++ destructors are not triggered by guile exceptions, and the dynwind mechanism is ill-suited for application to C++ data structures (in particular, STL structures). In my experience, writing a C++ function that takes data

Re: Patch for printing of system-error exceptions

Hi Krister, On Sat 28 Jul 2012 16:39, Krister Svanlund writes: > + (define (system-error-printer port key args default-printer) > +(apply (case-lambda > + ((func fmt reasons _) > + (format port "System error:\n") > + (apply format port fmt reasons)) >

Patch for printing of system-error exceptions

Wrote a really small patch for proper printing of system-error exceptions. I'm fairly certain it should work for most cases where it is thrown by guile. The patch is attached guile-system-error-printer.patch Description: Binary data

Exceptions

Hello, Neil Jerram writes: > Andy Wingo writes: > >> Oh man, at some point we have some pain coming, switching to >> srfi-35/r6rs exceptions. We mentioned it in August and decided to punt >> indefinitely -- though should someone be interested, help would be >> w