[erlang-questions] Behavio(u)r guard?
Fri Apr 15 21:37:43 CEST 2011
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?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions