8 messages in com.perforce.jammingMultiple compiles of the same file
FromSent OnAttachments
chri...@natinst.com chris.bartz@natinst.com29 Oct 1997 08:25 
Dian...@whistle.com29 Oct 1997 09:22 
jste...@kdc-tvcom.com jstewart@kdc-tvcom.com29 Oct 1997 09:32 
Paul...@biotype.biology.dal.ca29 Oct 1997 10:06 
Hunt...@unity.ncsu.edu29 Oct 1997 17:12 
"# Cowham, Robert Exchange CowhamR@logica.com30 Oct 1997 08:31 
Step...@PC-Plus.DE30 Oct 1997 08:32 
Tim ...@ftlsol.com30 Oct 1997 09:18 
Subject:Multiple compiles of the same file
From: ()
Date:10/30/1997 08:31:48 AM
List:com.perforce.jamming

Hunter Matthews <tpma@unity.ncsu.edu> writes:

It might make sense to correct the fact that jam sees each common.c/common.o as a separate entity (thus it would get on the data structure just once, and would be built just once.)

But, knowing a little of the history of Jam, I'm betting there's a good reason NOT to do that. Can you tell me what it is? (Jam's not "young" and I'm sure this has come up before. Since it wasn't changed/added, there must have been a reason).

Because you might want to compile the same target twice with different flags?

I believe this is the reason - it was what I was given when I asked the question back in March!

Robert