> > I've gone through the materials, and I have one question about the new
 > > behavior for ::print: how does it disambiguate the command line?
 > > 
 > > For example, if I do this:
 > > 
 > >    > ::walk foo | ::print bar
 > > 
 > > is "bar" a member of whatever sort of structure the "foo" list
 > > contains, or is "bar" the type of object I want to print in its
 > > entirety?
 > 
 > It builds upon the (possibly broken) current behavior:
 > 
 >      1.  if "bar" resolves as a type, we use that, or
 >      2.* if there's a valid pipe type, we use that, or
 >      3.  if addr is a symbol with associated type info, we use that.
 > 
 > (* is the new behavior).  This, unfortunately, has the DWIM nature, and
 > there's no current way to disambiguate it.

I would've expected one can override and get (3) by doing "::print `bar"

-- 
meem

Reply via email to