� wrote:
The GET-BACKTRACE function still remains as being non-portable.
Is there a possibility of splitting it off to a separate library too? It'll be just the thin portability layer, of course, but I can see some other possible uses for a hypothetical, well, say, chardonnay-backtraces library. For example some (non-web) delivered applications that could write backtraces to a log file to be examined by the author later, or to be emailed to the author.
Cheers, Ury