public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "André Albergaria Coelho" <andre1coelho@outlook.com>
To: linux-kernel@vger.kernel.org, libc-alpha@sourceware.org
Subject: c exceptions
Date: Fri, 21 Apr 2023 00:11:01 +0100	[thread overview]
Message-ID: <AM6PR03MB52829D01F2D7B49A7B504FEE93639@AM6PR03MB5282.eurprd03.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 454 bytes --]

what about if we use, on the c language, exceptions?
use it on a compiler flag, like gcc -exceptions
use a pointer function , to handle the exception (as in Java, catch{})
use macro to define which function has exceptions
does the exception throws another exception?
what happens to the call stack? can we print it
what happens to the stack? (if a function is used as a catch statement
Is the exception executed on a {} block?


thanks for time,


andre

             reply	other threads:[~2023-04-20 23:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 23:11 André Albergaria Coelho [this message]
2023-04-20 23:19 André Albergaria Coelho

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM6PR03MB52829D01F2D7B49A7B504FEE93639@AM6PR03MB5282.eurprd03.prod.outlook.com \
    --to=andre1coelho@outlook.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).