From 4d45627f8860fcc6fbb226bef3036bf76f2a48e8 Mon Sep 17 00:00:00 2001 From: Doug Kearns Date: Wed, 7 Jan 2009 14:48:15 +1100 Subject: [PATCH] Comment on 'new' in HACKING. --- HACKING | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/HACKING b/HACKING index 16d2d9c7..57d5f947 100644 --- a/HACKING +++ b/HACKING @@ -8,7 +8,7 @@ happy to accept your patches. First of all, all new features and all user-visible changes to existing features need to be documented. That means editing the appropriate help files -and adding a NEWS enty where appropriate. When editing the NEWS file, you +and adding a NEWS entry where appropriate. When editing the NEWS file, you should add your change to the top of the list of changes. If your change alters an interface (key binding, command) and is likely to cause trouble, prefix it with 'IMPORTANT:', otherwise, place it below the other 'IMPORTANT' @@ -116,9 +116,11 @@ We try to be quite consistent, but of course, that's not always possible. CompletionContext() could return a cached object. What's thesnowdog's opinion and why do you, Kris, think it's better/cleaner? - I don't think it's better/cleaner, it just seemed to be a concensus. + I don't think it's better/cleaner, it just seemed to be a consensus. --Kris + I don't like unnecessary use of 'new', I don't like 'new'. --djk + == Testing/Optimization == TODO: Add some information here about testing/validation/etc.