On 12/15/2014 06:32 AM, Andreas Lauser wrote:
I guess it's my turn to give two and a half cents of worthless opinions:
First, I think having a general logging facility is a good idea but I've got a
few technical and a more philosophical issues. Technical things first:
Now the non-technical concern:
- wouldn't it be better to wait until the Big Module Hierarchy Refactoring
(TM) is done so that the parser module does not need to host such general-
purpose infrastructure code? I mean, the dependencies between the modules are
already confusing enough as they are...
Wow! Ok! Great! Now this is exactly what I've been waiting for.
How do I get an invite to this "Big Module Hierarchy Refactoring"
party? I promise I'll be a well behaved bar_keep and mostly
listen.....(mostly).
Mapping out dependencies needs to start before this aforementioned
event, because, it often needs two or three "community efforts" before
being robustly resolved in such a way that future code developments can
move forward painlessly avoiding (or at least minimizing) such
confounding issues. In fact, minimally logging errors at both compile
time and runtime, especially related to inter-module dependencies should
also be part of this discussion?
Surely I'm most willing to listen to anyone's ideas on Module
dependencies issues, either what we have now or the way it should become
in the future.
cheers
Andreas
hth,
James
_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm
