| Re: [stellation-res] Adding artifact priority |
On Fri, Aug 09, 2002 at 09:27:15PM +0000, Mark C. Chu-Carroll wrote: > > All that really matters for an initial test is that Compound representing a > > directory (as all Compounds currently do) have a distinguished priority. I > > would suggest default priority of 0, with Compound having priority 1. > > I'd like to suggest doing something slightly different. I'd like the option > of putting things at both lower and higher priorities than compounds. So > I'd like to select a range for priorities - say 1-200. Then put compounds > right in the middle. Things that need to run before compounds > get priorities less than 100; things that run after the compounds > get priorities greater than 100. At the same priority, we don't > define the order. I'm not sure how large a priority range we want. I > think 200 should be plenty - I can't imagine 200 artifact agents! - but > people who make assumptions like that often get quoted years later > for their foolishness :-). > > Actually, how about just make the priorities an integer, let them be > signed, and run them in increasing order? Then we put Compound at 0, > which is a nice central distinguished position. That way, we've got as large a > range as we could possibly want. I think you need an extra bit to specify if the compound is ordered or not. The order of files in a directory is irrelevant. The order of lines in a source file is relevant. florin -- "If it's not broken, let's fix it till it is." 41A9 2BDE 8E11 F1C5 87A6 03EE 34B3 E075 3B90 DFE4
Attachment:
pgpcfLAUI9GZv.pgp
Description: PGP signature