[erlang-questions] Behavio(u)r guard?

[Mike Oxford]

I do not see any way to specify a behavior as a guard.
For a callback module, I cannot then say "if it's this kind of handler, ship
it over this way."

This is not critical or anything, but from a pure curiosity standpoint is
there an underlying reason, like there
is for not having is_string()?  Is the behavior/interface too soft to check
as a guard?

Thanks!!

-mox
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110415/9f5691f9/attachment.htm>