From: Andrew Haley <aph@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: typesafe symbols for C
Date: Mon, 31 Jan 2011 10:56:00 -0000 [thread overview]
Message-ID: <4D46830F.9020209@redhat.com> (raw)
In-Reply-To: <20110129205103.GB29226@nibiru.local>
On 01/29/2011 08:51 PM, Enrico Weigelt wrote:
> * Jonathan Wakely<jwakely.gcc@gmail.com> wrote:
>> On 3 January 2011 05:37, Enrico Weigelt wrote:
>>>
>>> Hi folks,
>>>
>>>
>>> is it somehow possible to let the C-compiler include some type
>>> information into symbol names (as IMHO done for C++) ?
>>
>> I don't think so.
>
> hmm. where should I start if I wanted to add that ?
>
>>> If not, what would have to be done for that ?
>>
>> Use a C++ compiler.
>
> hmm, maybe that's worth a try, but I doubt that all plain-C code
> will compile fine then.
It will be very close. One really good use of C++ is as C with
type-safe linkage.
Andrew.
next prev parent reply other threads:[~2011-01-31 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 5:44 Enrico Weigelt
2011-01-03 13:25 ` Jonathan Wakely
2011-01-29 22:33 ` Enrico Weigelt
2011-01-31 10:56 ` Andrew Haley [this message]
2011-01-31 12:29 ` Jonathan Wakely
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=4D46830F.9020209@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.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).