public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: tromey@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] tromey/operator-new-delete: add another note Date: Fri, 17 May 2013 20:29:00 -0000 [thread overview] Message-ID: <20130517202900.29408.qmail@sourceware.org> (raw) The branch, tromey/operator-new-delete has been updated via 822f1dafa18a9471407ff6faa3da8bdbb0b101c5 (commit) from 576fdaccce8bd759cdc63d9ae831d7028a8d8365 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit 822f1dafa18a9471407ff6faa3da8bdbb0b101c5 Author: Tom Tromey <tromey@redhat.com> Date: Fri May 17 14:28:55 2013 -0600 add another note ----------------------------------------------------------------------- Summary of changes: README.archer | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) First 500 lines of diff: diff --git a/README.archer b/README.archer index a328b6f..383a852 100644 --- a/README.archer +++ b/README.archer @@ -16,7 +16,6 @@ It is incomplete: when is this called? * No cookie is required if the new operator being used is ::operator new[](size_t, void*). - but we don't currently make a cookie for new Simple[7] * syntax for calling a destructor explicitly do we need to handle this specially? cannot be used with an implicit "this", must always be qualified @@ -31,3 +30,5 @@ It is incomplete: also a test for operator in namespace * operator delete with extra args + +* need tests for 'new' in gdb but delete from C++ hooks/post-receive -- Repository for Project Archer.
reply other threads:[~2013-05-17 20:29 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130517202900.29408.qmail@sourceware.org \ --to=tromey@sourceware.org \ --cc=archer-commits@sourceware.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: linkBe 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).