Crista still thinks that the Explicit Strategy Rule should be the default.
Do you have examples which show that this would be too restrictive?
Show some strategy/class graph combinations. For example, for
the strategy graph

{A->B
    B->C}

why is it useful to have a class graph which has an A between B and C.

-- Karl
=============
At the Demeter Seminar, Aug. 11, 1997, we decided to recommend
the following design guideline to Demeter/Java users (to address Crista's
concern):

=======================
The Explicit Strategy Rule:
If you prefer strategies which are explicit about all uses of the
class variables associated with the strategy graph nodes, add

bypassing {N1, N2, ... Nn}

to all strategy graph edges, where {N1, N2, ... ,Nn} is the set of all
class-valued variables appearing in the strategy.
=======================

Benefit: In the traversed paths the classes corresponding to the
class-valued variables can only appear as allowed by the strategy graph.

-- Karl