From: Richard Jones <rich@annexia.org>
To: Dmitry Bely <dmitry.bely@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Class runtime representation
Date: Mon, 10 Dec 2007 15:51:01 +0000 [thread overview]
Message-ID: <20071210155101.GA20671@furbychan.cocan.org> (raw)
In-Reply-To: <90823c940712100600h5d748658x5e4647169500a917@mail.gmail.com>
On Mon, Dec 10, 2007 at 05:00:41PM +0300, Dmitry Bely wrote:
> Thanks for the detailed explanation. I don't like method names in the
> binary because they show some implementation details that I would like
> to hide; several extra bytes of code are really not a problem.
I suppose you could preprocess the source to mangle method names, but
to be honest if you're worried about the security of the binary from
reverse engineering I'm afraid that you'll need to consider a lot more
than just mangling.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2007-12-10 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 13:59 Dmitry Bely
2007-12-07 14:36 ` [Caml-list] " Till Varoquaux
2007-12-07 15:16 ` Dmitry Bely
2007-12-08 13:36 ` Jacques Garrigue
2007-12-10 14:00 ` Dmitry Bely
2007-12-10 15:51 ` Richard Jones [this message]
2007-12-10 17:19 ` Dmitry Bely
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=20071210155101.GA20671@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=dmitry.bely@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 NNTP newsgroup(s).