On Tue, 30 Oct 2001, Peter Donald <[EMAIL PROTECTED]> wrote: > On Tue, 30 Oct 2001 20:16, Stefan Bodewig wrote: > >> All I've seen so far are a number of "I could live with this" >> statements, but no strong support for either option. > > I would prefer a manifest entry or flag in type library descriptor > or something like that if this was the path we chose to go.
"I could live with that" 8-) Seems we have three options left that didn't receive any -1s: (1) All tasks (and types) can be placed into an <init> construct which is much like a target, but cannot have dependencies of its own. All targets depend on this one implicitly. No tasks or types can be siblings of target. (2) All tasks (and types) can be siblings of targets. (3) Identify those tasks or types that can be siblings of targets by a flag inside the task library. I'm just trying to boil down the options, maybe we can finally come to a conclusion. Stefan who prefers option (1) but wouldn't veto the alternatives either. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
