[rt.cpan.org #80026] LIB is being in correctly quoted when using more than one lib path

[email protected] ("Sisyphus via RT")
Newsgroups perl.inline
Message-ID <[email protected]>
Fri Oct 05 21:56:10 2012: Request 80026 was acted upon.
Transaction: Correspondence added by SISYPHUS
       Queue: Inline
     Subject: LIB is being in correctly quoted when using more than one lib path
   Broken in: 0.48, 0.48_01, 0.48_02, 0.49, 0.49_01, 0.49_02, 0.50, 0.50_01, 0.50_02
    Severity: Important
       Owner: Nobody
  Requestors: [email protected]
      Status: new
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=80026 >


On Fri Oct 05 11:23:15 2012, JCLEMENTS wrote:
 
> I looked into the source and it looks like the quote_space subroutine 
> (C.pm line 84) is quoting the entire INC
> line("-I/opt/src/Bio-HMM-Logo-0.01/src/src
> -I/opt/src/Bio-HMM-Logo-0.01/src/easel") if I have more than one path. 

Thanks for the report, Jody.
I take it that if, in line 84, you replace "quote_space($value)" with
"$value", then everything is ok with 0.50 ?

The point of quote_space() was to (help) accommodate those who want to
put things in directories whose names contain white space (eg C:/Program
Files/).
It's a very poor situation, indeed, that in trying to accommodate insane
(and irritating) behaviour, a completely sane practice has been broken -
and I'll release a new version of Inline once I decide how to fix this.

I guess quote_space() needs to be able to distinguish between (insane)
spaces that are part of a directory name, and (sane) spaces that act as
a path separator ... but I haven't yet looked closely at this.

Cheers,
Rob
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.