logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

Re: [Module::Build] TODO for 0.28: msg#00113

Subject: Re: [Module::Build] TODO for 0.28
Dominique Quatravaux wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Randy W. Sims wrote:


If you really must have that alternate test_files syntax <g>, you
can try something like below. Warning it's not tested fully, and it
is only intended as an example. You may wish to fine tune the
behavior.


Quite impressive. But... Can you emulate this, too? :-) (from my
overloaded cull_args)

sub cull_args {
    #[...]
    # XEmacs foolishly assumes that the second word in the perldb
    # line is a filename and turns it into e.g. "/my/path/test":
        my (undef, undef, @realargv) =
            File::Spec->splitpath(shift @argv);
    # [... Populate @realargv some more, code omitted ... ]

    return $self->SUPER::cull_args(@argv);
}

Actually, I was thinking the emacs stuff would be better integrated into M::B itself if it can be done in a clean and minimal way. My example was more to demonstrate a method of allowing test files to be listed on the commandline the way you wanted.

I still haven't had time to review your module to figure out which parts are necessary to better support emacs debugger running test files.

(I'd prefer to avoid exposing cull_args, etc. until properties have
been integrated.)


How would they both interfere? And wouldn't it be good enough to
explain in the POD that one needs to call ->SUPER::cull_args() exactly
once from within an overloaded ->cull_args()?

I'm being paranoid. I'm not sure what it will look like when I integrate the properties/commandline processing stuff. Most everything under cull_args() will mostly disappear as it has been reimplemented in the new module, but it's probable that cull_args() itself will remain. I'm just trying to avoid promising more than absolutely necassary to give myself more flexibility.

If you can't get what you need from manipulating @ARGV in the documented new() and resume() constructors or defining commandline options via get_options or pulling name=value pairs from $self->args('name') or grabbing the leftover args from $self->args('ARGV'), we can expose cull_args(). ;)

Randy.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click


<Prev in Thread] Current Thread [Next in Thread>