[Seaside-dev] Issue 227 in seaside: #halt should always halt
codesite-noreply at google.com
codesite-noreply at google.com
Sun Nov 2 10:34:45 UTC 2008
Issue 227: #halt should always halt
http://code.google.com/p/seaside/issues/detail?id=227
Comment #7 by renggli:
I disagree. We should follow the principle of least surprise and always
show a #halt as a debugger popping up. If
you have a #halt in your production code that's your problem (lint detects
that, and monticello should do that
too as it was done in ancient change-set file-outs).
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
More information about the seaside-dev
mailing list