job000017 #7

  • //
  • spec/
  • job/
  • job000017
  • View
  • Commits
  • Open Download .zip Download (3 KB)
# 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:	job000017

Status:	closed

Project:	jam

Severity:	C

ReportedBy:	craig_mcpheeters

ReportedDate:	2002/02/26 10:36:08

ModifiedBy:	shawn_hladky

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

Description:
	Superfluous :E in Jambase
	
	Date: Fri, 15 Feb 2002 23:35:12 -0800 (PST)
	From: [email protected] (Craig McPheeters)
	Message-Id: <[email protected]>
	To: [email protected]
	Subject: Tiny fix to Jambase
	
	...
	
	ps.  If you want really small 'problems'...on line 984 the use of
	$(SEARCH_SOURCE:E) isn't needed, its simply $(SEARCH_SOURCE).  No :E required.
	(In the comment above it too.)

DevNotes:
	| Hi Again, Craig.
	| 
	|         HDRSEARCH on $(>) =
	|                 $(SEARCH_SOURCE:E) $(SUBDIRHDRS) $(HDRS) $(STDHDRS) ;
	| 
	| 
	| Are you very sure about this one? The $(SEARCH_SOURCE:E) looks very
	| intentional, and I think I discern at least a glimmer of difference
	| with vs. without the :E). I.e., _with_ it, and if/when SEARCH_SOURCE
	| is undefined, HDRSEARCH would get a four-element list (the first being
	| an empty string). Without it, HDRSEARCH would get a three-element list
	| value.
	| 
	| Might it be possible that some compilers on some platforms would need
	| an explicit -I"" (or equivalent) in order to case the cwd to be
	| searched? Or that Jam itself needs this in order to properly find
	| #included files in the cwd?
	| 
	| Is there any actuall negative impact you know of to having it there?
	| if not, I'd be tempted to leave it in for 2.4 at least.
	| 
	| (I'll also see if Christopher has anything to say on it).
	| 
	|   -rmg
	| 	
	
	(seiwald)
	
	Just a few lines above it says:
	
	# $(SEARCH_SOURCE:E) is where cc first looks for #include
	# "foo.h" files.  If the source file is in a distant directory,
	# look there.  Else, look in "" (the current directory).
	
	Seems pretty intentional.
# Change User Description Committed
#7 default
#6 default
#5 default
#4 default
#3 default
#2 default
#1 default