IMO the problem is that this comment is too vague and things must be
explained better in commit comments/jira issues (Alessandro let's say
you where in a hurry, right?).
Yes, I think that's the point here. Cut the problems into smaller
pieces that others can follow and create issues for each sub-problem.
The commit message was then misleading in this case.
I understand the confusion. To be more precise, that commit was a
temporary, quick albeit computationally sub-optimal solution, which I
thought qualified it as a hack. Maybe it doesn't then?
It was BTW what caused the last step of my EA demo to run slow, as a
price paid against not delivering results at all before we applied it.
Or at least immediately create a JIRA issue that's about removing
those hacks, so that we don't forget to cleanup. Depends on how bad
the hacks are I guess.
Right you are, will do. Sorry for the misunderstanding this has caused.
Alessandro
--
M.Sc. Alessandro Adamou
Alma Mater Studiorum - Università di Bologna
Department of Computer Science
Mura Anteo Zamboni 7, Bologna - Italy
Semantic Technology Laboratory (STLab)
Institute for Cognitive Science and Technology (ISTC)
National Research Council (CNR)
Via Nomentana 56, 00161 Rome - Italy
"As for the charges against me, I am unconcerned. I am beyond their timid, lying
morality, and so I am beyond caring."
(Col. Walter E. Kurtz)
