From: Eric Wong <normalperson@yhbt.net>
To: Sam Vilain <sam.vilain@catalyst.net.nz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-svn: avoid string eval for defining functions
Date: Fri, 15 Jun 2007 17:22:54 -0700 [thread overview]
Message-ID: <20070616002254.GB26502@untitled> (raw)
In-Reply-To: <11818790393274-git-send-email-sam.vilain@catalyst.net.nz>
Sam Vilain <sam.vilain@catalyst.net.nz> wrote:
> You don't need to use string eval to define new functions; assigning a
> code reference to the target symbol table is enough.
Cool.
Acked-by: Eric Wong <normalperson@yhbt.net>
> ---
> git-svn.perl | 64 +++++++++++++++++++++++++++++----------------------------
> 1 files changed, 33 insertions(+), 31 deletions(-)
>
> diff --git a/git-svn.perl b/git-svn.perl
> index 4d35895..4ba0813 100755
> --- a/git-svn.perl
> +++ b/git-svn.perl
> @@ -38,14 +38,16 @@ use IPC::Open3;
> use Git;
>
> BEGIN {
> - my $s;
> + # import functions from Git into our packages, en masse
> + no strict 'refs';
> foreach (qw/command command_oneline command_noisy command_output_pipe
> command_input_pipe command_close_pipe/) {
> - $s .= "*SVN::Git::Editor::$_ = *SVN::Git::Fetcher::$_ = ".
> - "*Git::SVN::Migration::$_ = ".
> - "*Git::SVN::Log::$_ = *Git::SVN::$_ = *$_ = *Git::$_; ";
> + for my $package ( qw(SVN::Git::Editor SVN::Git::Fetcher
> + Git::SVN::Migration Git::SVN::Log Git::SVN),
> + __PACKAGE__) {
> + *{"${package}::$_"} = \&{"Git::$_"};
> + }
> }
> - eval $s;
> }
>
> my ($SVN);
> @@ -898,26 +900,26 @@ BEGIN {
> # some options are read globally, but can be overridden locally
> # per [svn-remote "..."] section. Command-line options will *NOT*
> # override options set in an [svn-remote "..."] section
> - my $e;
> - foreach (qw/follow_parent no_metadata use_svm_props
> - use_svnsync_props/) {
> - my $key = $_;
> + no strict 'refs';
> + for my $option (qw/follow_parent no_metadata use_svm_props
> + use_svnsync_props/) {
> + my $key = $option;
> $key =~ tr/_//d;
> - $e .= "sub $_ {
> - my (\$self) = \@_;
> - return \$self->{-$_} if exists \$self->{-$_};
> - my \$k = \"svn-remote.\$self->{repo_id}\.$key\";
> - eval { command_oneline(qw/config --get/, \$k) };
> - if (\$@) {
> - \$self->{-$_} = \$Git::SVN::_$_;
> + my $prop = "-$option";
> + *$option = sub {
> + my ($self) = @_;
> + return $self->{$prop} if exists $self->{$prop};
> + my $k = "svn-remote.$self->{repo_id}.$key";
> + eval { command_oneline(qw/config --get/, $k) };
> + if ($@) {
> + $self->{$prop} = ${"Git::SVN::_$option"};
> } else {
> - my \$v = command_oneline(qw/config --bool/,\$k);
> - \$self->{-$_} = \$v eq 'false' ? 0 : 1;
> + my $v = command_oneline(qw/config --bool/,$k);
> + $self->{$prop} = $v eq 'false' ? 0 : 1;
> }
> - return \$self->{-$_} }\n";
> + return $self->{$prop};
> + }
> }
> - $e .= "1;\n";
> - eval $e or die $@;
> }
>
> my %LOCKFILES;
> @@ -2956,17 +2958,17 @@ my ($can_do_switch, %ignored_err, $RA);
>
> BEGIN {
> # enforce temporary pool usage for some simple functions
> - my $e;
> - foreach (qw/rev_proplist get_latest_revnum get_uuid get_repos_root/) {
> - $e .= "sub $_ {
> - my \$self = shift;
> - my \$pool = SVN::Pool->new;
> - my \@ret = \$self->SUPER::$_(\@_,\$pool);
> - \$pool->clear;
> - wantarray ? \@ret : \$ret[0]; }\n";
> + no strict 'refs';
> + for my $f (qw/rev_proplist get_latest_revnum get_uuid get_repos_root/) {
> + my $SUPER = "SUPER::$f";
> + *$f = sub {
> + my $self = shift;
> + my $pool = SVN::Pool->new;
> + my @ret = $self->$SUPER(@_,$pool);
> + $pool->clear;
> + wantarray ? @ret : $ret[0];
> + };
> }
> -
> - eval "$e; 1;" or die $@;
> }
>
> sub new {
> --
> 1.5.2.0.45.gfea6d-dirty
>
--
Eric Wong
prev parent reply other threads:[~2007-06-16 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 3:43 [PATCH] git-svn: avoid string eval for defining functions Sam Vilain
2007-06-16 0:22 ` Eric Wong [this message]
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=20070616002254.GB26502@untitled \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=sam.vilain@catalyst.net.nz \
/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;
as well as URLs for NNTP newsgroup(s).