From: Nick Clifton <nickc@redhat.com>
To: Cut Hour <cuthour@gmail.com>, binutils@sourceware.org
Subject: Re: Old story (30 years ago)
Date: Tue, 24 Jan 2023 13:27:19 +0000 [thread overview]
Message-ID: <023b1467-8a49-5380-40cb-a4e7d8d66c19@redhat.com> (raw)
In-Reply-To: <3a337aa1-032b-1d19-8c42-db8a117841c0@gmail.com>
Hi Cut Hour,
>> This is not to say that exploring the idea is not worthwhile. It
>> might produce some interesting results. But I would be hesitant about
>> applying it to a generic tool like the linker without a real need.
>
> I myself had needed it. My plan was like this. Every instance has a
> ptr to its class. Every class has a method table (array of ptr to
> function). All methods are called via a ptr in the method table.
> The syntax is almost the same as ObjC. Binutils (for the structured
> programming) is what makes this simplest OO language so hard to come
> by. Neither C++ nor ObjC nor Java pointed that out. Again, is this
> cleared in LLVM?
I do not think so. I cannot say for sure, but linking with LLVM (and
its linker LLD) is basically the same process as used by the binutils
linker. The implementations differ, but what they do is basically the
same.
Cheers
Nick
prev parent reply other threads:[~2023-01-24 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 10:21 Cut Hour
2023-01-17 13:55 ` Nick Clifton
2023-01-17 15:28 ` Cut Hour
2023-01-24 13:27 ` Nick Clifton [this message]
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=023b1467-8a49-5380-40cb-a4e7d8d66c19@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=cuthour@gmail.com \
/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).