From: Brad Fisher <brad@info-link.net>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] Minor fix for patchlets which modify multiple projects
Date: Thu, 13 May 2004 11:09:42 -0500 [thread overview]
Message-ID: <40A39DC6.C3F78CA3@info-link.net> (raw)
In-Reply-To: 40A2E52C.3010103@trash.net
Patrick McHardy wrote:
> Thanks Brad, I've applied a small variation of this, because I don't know if
> perl will complain about two equally named variables (@projects and %projects)
> with warnings turned on.
I don't think your patch is quite right. You can end up having the same project listed multiple
times with your patch, which is why I used the separate hash - key collisions are reduced to single
entries. I guess as long as it is no problem for a project to be processed multiple times, then
your patch will be OK, but if that isn't the case, you may want to look into it again.
As far as variables with the same name and different types, I don't believe Perl complains. I
typically program with 'use strict', which I believe enables all warnings, and have used naming
like this before. Of course it does add quite a bit of ambiguity, so renaming the %projects hash
would probably be a good idea if you choose to use a variation of my patch.
> Regards
> Patrick
-Brad
next prev parent reply other threads:[~2004-05-13 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 19:04 [PATCH] Minor fix for patchlets which modify multiple projects Brad Fisher
2004-05-13 3:02 ` Patrick McHardy
2004-05-13 16:09 ` Brad Fisher [this message]
2004-05-13 18:08 ` Patrick McHardy
2004-05-14 8:32 ` Jozsef Kadlecsik
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=40A39DC6.C3F78CA3@info-link.net \
--to=brad@info-link.net \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.