in reply to Re^16: Perl 5 Optimizing Compiler, Part 4: LLVM Backend?
in thread Perl 5 Optimizing Compiler, Part 4: LLVM Backend?
You do realize your idea will break $^E?
It not "my idea"....
Please think about the following sequence of events:
Program enters C ...
Still in C
Still in C
But we must preserve that extended error information
So that when we get around to telling the user that the other API we called, failed,
he can query for some extra information
Think. What API might we be calling at 3, that fails, but not so badly that we can't fiddle with the context, before we report that failure back to user, who might want to get the extended error information?
And, if SetContext should fail, is the extended error information from that mysterious API still important? Will we ever get back to the user for him to be able to query that extended error information?
Details. Details... Off topic. Let's stop.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^18: Perl 5 Optimizing Compiler, Part 4: LLVM Backend?
by bulk88 (Priest) on Aug 30, 2012 at 17:09 UTC | |
by BrowserUk (Patriarch) on Aug 30, 2012 at 17:22 UTC |