SourceForge has been redesigned. Learn more.
Close

#203 Uninformative quasi-match failure messages

Need_for_debugging
closed-fixed
2
2005-07-24
2005-07-15
No

FIXED
The protocol of MatchMakers used to be to return null
to indicate failure. This meant that on failure to
match, the MatchMaker had no useful way to indicate why
the match failed.

Followups

Comment Date By
We changed the protocol so that a MatchMaker indicates
failure by calling an ejector.

? interp.setExpand(true)

? def `foo` := "bar"
# expansion: def pair_1 :__MatchContext ? (def [q_3,
optEj_5] := pair_1
#
simple__quasiParser.matchMaker("foo").matchBind(__makeList.run(),
q_3, optEj_5) =~ []) := "bar"

# problem: Prefix doesn't match: foo
2004-Jan-27 04:16 markm

Discussion

  • Steve Jenson

    Steve Jenson - 2005-07-18
    • status: open --> closed-fixed
     
  • Mark Samuel Miller

    • assigned_to: nobody --> caplet
     

Log in to post a comment.