I don't think so.  I renamed Window.pm in blib then checked to see where it was 
pulling Window.pm from:

$ ls blib/lib/PDL/Graphics/PGPLOT/
Window.pmc       renamedWindow.pm
$ perl -Mblib -MPDL::Graphics::PGPLOT::Window -wE 'say 
$INC{q|PDL/Graphics/PGPLOT/Window.pm|};'
/Users/derek/Build/pdl-code/blib/lib/PDL/Graphics/PGPLOT/Window.pm

Looks sane to me.

> On Feb 25, 2015, at 5:44 PM, Ed <ej...@hotmail.com> wrote:
> 
> Pulling in installed, working version?
>  
> From: Derek Lamb <mailto:de...@boulder.swri.edu>
> Sent: Thursday, February 26, 2015 12:32 AM
> To: pdl-devel@lists.sourceforge.net <mailto:pdl-devel@lists.sourceforge.net>
> Subject: Re: [Pdl-devel] PDL::NiceSlice engine is slow (again)
>  
> <snip>
>  
> Oddly, once I compile Window.pm into a .pmc I get no warnings and no syntax 
> error at line 2693, even though that line has not been touched by the source 
> filter.  So I'm not sure what's going on there.  Ideas?
>  
> best,
> Derek
>  
>  
>> On Feb 25, 2015, at 2:37 PM, Chris Marshall <devel.chm...@gmail.com 
>> <mailto:devel.chm...@gmail.com>> wrote:
>>  
>> Derek, is the 0.7sec->13sec trouble module code you can share?
>> Regardless, any PDL::NiceSlice for our official release should not
>> have performance issues like that. 
>> 
>> --Chris
>>  
>> On Wed, Feb 25, 2015 at 4:34 PM, Chris Marshall <devel.chm...@gmail.com 
>> <mailto:devel.chm...@gmail.com>> wrote:
>>> Hi Karl-
>>> 
>>> As I mentioned the current setting is to test/exercise/debug
>>> the more correct parsing to not apply the PDL::NiceSlice
>>> filter to the content of POD, comments, or string bodies.
>>> 
>>> Even so, you can set the PDL_NICESLICE_ENGINE environment
>>> variable to 'Filter::Util::Call' to have the original fast, in-exact
>>> processing with the current CPAN devel release.
>>> 
>>> --Chris
>>> 
>>> On Wed, Feb 25, 2015 at 4:24 PM, Karl Glazebrook <karlglazebr...@mac.com 
>>> <mailto:karlglazebr...@mac.com>> wrote:
>>>> I would say there is no excuse for 13 seconds!
>>>> 
>>>> - Karl
>>>>  
>>>> 
>>>> On 26 Feb 2015, at 8:01 am, Chris Marshall <devel.chm...@gmail.com 
>>>> <mailto:devel.chm...@gmail.com>> wrote:
>>>> 
>>>>> Hi Derek-
>>>>> 
>>>>> The current setting for the PDL::NiceSlice engine is
>>>>> for checking that the implementation works.  I appreciate
>>>>> the problem report.  I'm not able to directly check since
>>>>> I can no longer build pgplot on cygwin so I don't have
>>>>> PGPLOT either.
>>>>> 
>>>>> The performance difference with the new NiceSlice engine
>>>>> is due to the fact that it is unoptimized in that it
>>>>> preprocesses the entire file before applying the souce
>>>>> filter where needed.
>>>>> 
>>> ...snip...
>> 
>>  
> 
>  
> _______________________________________________
> pdl-devel mailing list
> pdl-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pdl-devel

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
pdl-devel mailing list
pdl-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pdl-devel

Reply via email to