From: Caspar Zhang <caspar@casparzhang.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>,
Mike Frysinger <vapier@gentoo.org>
Subject: Re: [LTP] [PATCH 0/4] Replace commonly used perl tools with awk equivalents
Date: Sat, 07 Apr 2012 00:19:08 +0800 [thread overview]
Message-ID: <4F7F177C.50100@casparzhang.com> (raw)
In-Reply-To: <CAGH67wQcNtAkP4aMmGELSyEavEx-AbWqhjJxd_M-mh-u6qdn+w@mail.gmail.com>
On 04/06/2012 11:34 AM, Garrett Cooper wrote:
> On Wed, Apr 4, 2012 at 6:49 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>> On Wednesday 04 April 2012 20:33:40 Garrett Cooper wrote:
>>> On Wed, 4 Apr 2012, Mike Frysinger wrote:
>>>> On Wednesday 04 April 2012 15:18:53 Garrett Cooper wrote:
>>>>> On Wed, Apr 4, 2012 at 10:54 AM, Mike Frysinger wrote:
>>>>>> On Wednesday 04 April 2012 13:31:10 Garrett Cooper wrote:
>>>>>>> On Wed, Apr 4, 2012 at 10:22 AM, Mike Frysinger wrote:
>>>>>>>> On Wednesday 04 April 2012 01:23:43 Garrett Cooper wrote:
>>>>>>>>> The intent behind these changes are to remove unnecessary perl
>>>>>>>>> dependencies in LTP by using awk in its stead. It was something that
>>>>>>>>> was discussed a while ago on ltp-list@.
>>>>>>>>
>>>>>>>> i like awk over perl a lot. my only concern is non-POSIX stuff
>>>>>>>> slipping in (such as people who have gawk installed). should we add
>>>>>>>> a local wrapper script that sees if the awk accepts a --posix flag
>>>>>>>> and automatically pass it ?
>>>>>>>
>>>>>>> That's actually a gawk-ism :)...
>>>>>>
>>>>>> yes, that's why i phrased it "if the awk accepts"
>>>>>>
>>>>>> awk --help | grep -q -e --posix && args="${args} --posix"
>>>>>
>>>>> This makes sense and it would protect against gawk'isms, but not other
>>>>> *awk-isms.
>>>>
>>>> sure, but some protection is better than none. if other awks have
>>>> similar knobs, we can leverage them too.
>>>
>>> Agreed, but this should be handled in other commits, right?
>>
>> sure, i'm not saying let's hold up the conversion from perl. but we should do
>> it at some point imo.
>
> Are there any objections to the proposed [final?] patches I
> submitted for this patch set?
> Thanks!
looks good to me.
Reviewed-by: Caspar Zhang <caspar@casparzhang.com>
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-04-06 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 5:23 [LTP] [PATCH 0/4] Replace commonly used perl tools with awk equivalents Garrett Cooper
2012-04-04 17:22 ` Mike Frysinger
2012-04-04 17:31 ` Garrett Cooper
2012-04-04 17:54 ` Mike Frysinger
[not found] ` <201204042028.52373.vapier@gentoo.org>
[not found] ` <alpine.BSF.2.00.1204041732320.25027@toaster.local>
[not found] ` <201204042149.20439.vapier@gentoo.org>
2012-04-06 3:34 ` Garrett Cooper
2012-04-06 16:19 ` Caspar Zhang [this message]
2012-04-07 2:31 ` Wanlong Gao
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=4F7F177C.50100@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vapier@gentoo.org \
--cc=yanegomi@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