The ideal situation for a developer from a compile standpoint would be to "stack" the production and development libraries in the compile list so that they'd actually only need to maintain a small subset of templates in their local environment. For example, the template list would first point to the production directory, and then to the local development directory. Any template that had a duplicate on the local (second) directory would be compiled again, such that the test version would be used, and the production version discarded. I believe this would help in version control for those that don't have a formal check-in check-out product.

Append

By: WindSurfer When: 1998-12-18 10:09:31 New Status:
Pending Customer

Comment

Don't you mean that the test directory would be first in the list? This would be more like the way the PATH statement in DOS and other OpSys's has worked, as well as INCLUDE and other paths for compiled development.

This is also a lot easier for us to code :) (duplicates are ignored after compiling the first encountered, rather than backing-out what is already there).

Append

By: PeteL When: 1998-12-18 10:13:20 New Status:
Pending IE

Comment

from a logical point of view, it doesn't really matter, the secondary (tirtiary, etc.) compiles would just overlay the prior one in my example, the other way is equally effective and, if easier to code and more consistent with precedent, would seem preferable.

Append

By: WindSurfer When: 1999-01-05 16:01:03 New Status:
Pending Customer

Comment

Now available--

ftp://ftp.ieinc2.com/pub/surfer/t1_3_28e.zip contains new ielua.exe with duplicates ignored. A warning is issued for each duplicate file, but this is not counted as an "error" for the summary line of the compiler.

To use, you utilize a compile listing file, and then name individual files or directory names in the order that you want them compiled. First file of a given name (from any directory) is the only one used; any duplicates are ignored with a warning issued during the compile.

Append

By: PeteL When: 1999-01-19 11:17:41 New Status:
Pending IE

Comment

I tried adding some network-based (test server) templates to the bottom of my template list, expecting to trigger the warning message about duplicates, but instead got

Please check your file path-- just tested with a network drive specified file and it worked fine...

Is your file a duplicate or unique?

Append

By: PeteL When: 1999-01-19 12:09:42 New Status:
Pending IE

Comment

duplicate, done on purpose to check the outcome

Append

By: PeteL When: 1999-01-19 12:28:07 New Status:
Pending IE

Comment

OK, now I checked the comment capability as specified in trouble ticket #201, and the double-forward slash was not interpreted as a comment, it still tried to process the line as a filename.

Append

By: WindSurfer When: 1999-01-19 13:41:46 New Status:
Pending Customer

Comment

Comment had a bug on the most common case of starting the line with a comment...if you start the line with at least one blank, then a comment (//) it works...silly us for testing the ability to end a line with a comment but not have simply a comment line.