#797
- Created on2011-03-04 11:13
- Reported by
- StatusFixed
- PriorityNormal (3)
- Assigned to
- Milestone
- Plan Level-
- EstimateNone/Small/Medium/Large None
- Due Date-
model - the splitting into function clauses is too simple, causing bad code formatting
In this case:
the is_list is taken for a new clause. The noparse-splitting into function clauses needs to be a bit more intelligent. (And no, we're not going to use syntax tools, of reasons stated before.)
foo() ->
case A of
?CHST_HRL when is_integer(A);
is_list(A) ->the is_list is taken for a new clause. The noparse-splitting into function clauses needs to be a bit more intelligent. (And no, we're not going to use syntax tools, of reasons stated before.)
Leave a comment
on 2011-04-13 14:05 *
By jakobc
Summary changed from model - the splitting into function clauses is too simple to model - the splitting into function clauses is too simple, causing bad code formatting
Summary changed from model - the splitting into function clauses is too simple to model - the splitting into function clauses is too simple, causing bad code formatting