7 messages in com.perforce.jamming[jamming] quoting?
FromSent OnAttachments
Craig Allsop14 Jan 2003 17:11 
davi...@rcn.com14 Jan 2003 17:52 
Chris Antos14 Jan 2003 18:10 
Craig Allsop15 Jan 2003 00:32 
Chris Antos15 Jan 2003 12:17 
Craig Allsop15 Jan 2003 14:47 
Chris Antos15 Jan 2003 15:53 
Subject:[jamming] quoting?
From:Craig Allsop (call@auran.com)
Date:01/15/2003 12:32:51 AM
List:com.perforce.jamming

Hi Chris.

As far as I'm aware commands will never see the quotes because the shell would remove them. If someone doesn't use this character in filenames the execution of jam will be the same as it is now.

Craig.

----- Original Message ----- From: "Chris Antos" <chri@windows.microsoft.com> To: <jamm@perforce.com> Sent: Wednesday, January 15, 2003 12:11 PM Subject: RE: [jamming] quoting?

I know of some tools on Windows at least that do not accept quoted paths, for whatever reason. The reasons don't really matter, since the tools exist and are used. :-) Doesn't seem like a good idea to hard code it that way.

-----Original Message----- From: davi@rcn.com [mailto:davi@rcn.com] Sent: Tuesday, January 14, 2003 5:53 PM To: Craig Allsop Cc: jamm@perforce.com Subject: Re: [jamming] quoting?

David Abrahams <da@boost-consulting.com> writes:

Craig Allsop <call@auran.com> writes:

Hi guys.

Should the jambase out-of-the-box handle filenames that contain the "&" character? e.g.

DIR = [ FDirName a b&b c ] ; Depends all : $(DIR) ; MkDir $(DIR) ;

It would appear to me the best place to deal with this is in the actions by adding double quotes around filenames. This seems to work ok for unix/windows for us so far.

I have considered the idea of changing Jam to automatically quote all bound target names when the appear in actions. I've never tried it, though, and I'm not sure whether it would work.

http://maillist.perforce.com/mailman/listinfo/jamming

Auran disclaims responsibility for the contents of this e-mail unless it was expressly authorised by Auran. This e-mail is a confidential communication. To the extent permitted by law, Auran does not accept any liability for any loss or damage suffered or incurred by you as a result of receiving, opening or relying on this e-mail.