job000010 #7

# Perforce Public Depot Jobs
#
#  Job:           The job name. 'new' generates a sequenced job number.
#  Status:        Job status; [open/closed/suspended].  Required
#  Project:       The project this job is for [none/cdsp4/jam/p4hl]  Optional.
#  Severity:      [A/B/C] (A is highest)  Required.
#  ReportedBy     The user who created the job. Can be changed.
#  ReportedDate:  The date the job was created.  Automatic.
#  ModifiedBy:    The user who last modified this job. Automatic.
#  ModifiedDate:  The date this job was last modified. Automatic.
#  OwnedBy:       The owner, responsible for doing the job. Optional.
#  Description:   Description of the job.  Required.
#  DevNotes:      Developer's comments.  Optional.

Job:	job000010

Status:	closed

Project:	jam

Severity:	A

ReportedBy:	matt_armstrong

ReportedDate:	2002/02/25 15:39:27

ModifiedBy:	shawn_hladky

ModifiedDate:	2008/04/13 13:00:54

OwnedBy:	richard_geiger

Description:
	Change in "if $(VAR) in v1 v2 v3" behavior
	
	Until recent versions of Jam, this used to be perfectly legal syntax.
	
	    VAR = value3 ;
	    if $(VAR) in value1 value2 value3 value4 value5 {
	        ECHO yep ;
	    } else {
	        ECHO nope ;
	    }
	
	And Jam would echo "yep."
	
	Now it issues an error "syntax error at argument value2."  We've got
	this construct sprinkled throughout our Jamfiles.
	
	See also: http://maillist.perforce.com/pipermail/jamming/2002-February/001590.html

DevNotes:
	Assume this means a change since 2.3.2