Hello Andrew, I could not identify any __stdcall Windows API function that would allow catching abort() as raised by xfault(). Without such a function I will not be able to stop the termination of Excel or any VBA applications using the GLPK library. This is why I am requesting the hook.
Best regards Xypron -------- Original-Nachricht -------- > Datum: Wed, 19 Mar 2008 10:33:40 +0300 > Von: Andrew Makhorin <[EMAIL PROTECTED]> > An: "glpk xypron" <[EMAIL PROTECTED]> > CC: help-glpk@gnu.org, [EMAIL PROTECTED], [EMAIL PROTECTED] > Betreff: Re: [Help-glpk] Hook needed in xfault() > > if an error occurs in the GLPK library xfault is called and > > executes abort(). This is permissible in GLPSOL. > > > In other programs using the library this behavior causes trouble: > > - The calling program cannot release objects and libraries. > > - The user of a GUI program cannot save his prior work. > > > Please, provide a hook function in xfault() (in glib05.c). > > > If the hook is set, abort() should not be executed. Instead the > > calling program shall decide what to do next. > > There is a standard way to achive the same effect, namely, catching > the signal SIGABRT with the user-defined signal handler. > -- Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! http://games.entertainment.gmx.net/de/entertainment/games/free _______________________________________________ Help-glpk mailing list Help-glpk@gnu.org http://lists.gnu.org/mailman/listinfo/help-glpk
