From: Ingo Krabbe <ikrabbe.ask@web.de>
To: gcc-help@gcc.gnu.org
Subject: Re: C++ operators in gcc
Date: Sat, 24 Sep 2005 09:03:00 -0000 [thread overview]
Message-ID: <200509241103.34262.ikrabbe.ask@web.de> (raw)
In-Reply-To: <200509232348.08931@gj-laptop>
Does this really make the binary file a bit larger. I don't think so. Every
class you define (or structure with C) is automatically be able to be copied
(in a flat manner of course) by the operator =. I think that someone who
told you meant that behaviour, that is part of the ISO definition as I
suppose and as such not specific to gcc.
I assume there would be no single byte of code blow up for this behaviour.
BYE INGO
Am Freitag, 23. September 2005 23:48 schrieb Tommy Vercetti:
> Hi list
>
> I was told that gcc by default, for every class creates operator =, and
> probably something else. This makes binary file bit larger than it suppose
> to be. Is it true, and if so, why this is the case ? Can gcc simply not
> generate that operator?
>
> please CC me on replies.
next prev parent reply other threads:[~2005-09-24 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 21:48 Tommy Vercetti
2005-09-24 9:03 ` Ingo Krabbe [this message]
2005-09-26 11:21 ` John Love-Jensen
2005-09-26 18:40 ` Ingo Krabbe
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=200509241103.34262.ikrabbe.ask@web.de \
--to=ikrabbe.ask@web.de \
--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).