[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1254888565.28917.135.camel@tropicana>
Date: Tue, 06 Oct 2009 23:09:25 -0500
From: Tom Zanussi <tzanussi@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel@...r.kernel.org, fweisbec@...il.com,
rostedt@...dmis.org, lizf@...fujitsu.com, hch@...radead.org
Subject: Re: [RFC][PATCH 5/9] perf trace: Add Perl scripting support
On Tue, 2009-10-06 at 15:00 +0200, Ingo Molnar wrote:
> * Tom Zanussi <tzanussi@...il.com> wrote:
>
> > OPT_BOOLEAN('v', "verbose", &verbose,
> > "be more verbose (show symbol address, etc)"),
> > + OPT_BOOLEAN('p', "perl", &do_perl,
> > + "send output to a Perl script"),
> > OPT_STRING('s', "script", &script_name, "file",
> > "script file name"),
>
> I dont think we want to use up primary option letters one per language.
> If Perl takes 'p' then what will Python use, 'P'? How about PHP, PEARL
> and PostScript then? ;-)
>
> I think it's better to make the language specification part of the
> -s/--script option, via two methods:
>
> Explicit:
>
> -s Perl::my_script.pl
> -s pl::my_script.pl
> -s Python::my_script.py
> -s Bash::my_script.sh
>
> Implicit, based on the script extension:
>
> -s my_script.pl # maps to the Perl generator
> -s my_script.py # maps to the Python generator
> -s my_script.sh # maps to the Bash generator
>
> I think we also want to have a 'perf -s *' kind of thing to get a list
> of all available language modules.
>
I knew somebody would point that out (and suggest a better way ;-) That
all makes sense - I'll make these changes in the next version.
Tom
> Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists