[
https://issues.apache.org/jira/browse/JOSHUA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267566#comment-15267566
]
Matt Post commented on JOSHUA-260:
----------------------------------
This looks cool. I am not going to be able to look into it until June, but we
could chat about it next week.
Can you say more about how this interacts with the config system? I'd love to
see that overhauled. It would be really nice to do better argument processing.
The features I like in the current system are:
- being able to list all parameters in a config file, but then to override them
on the command line
- (nice but less important) collapsing different arguments to equiv. classes
(e.g., "top-n" = "topn" = "topN" etc)
It would be nice to have:
- builtin documentation to each parameter
- the ability to invoke the decoder with -help
My 20 second look at guice though seems to suggest this is something quite
different, though?
> Integrate IoC (Inversion of Control) into Joshua
> ------------------------------------------------
>
> Key: JOSHUA-260
> URL: https://issues.apache.org/jira/browse/JOSHUA-260
> Project: Joshua
> Issue Type: Improvement
> Reporter: Kellen Sunderland
>
> I'd like to propose we investigate looking into using guice
> (https://github.com/google/guice) in conjunction with joshua's configuration
> system. I believe it would give us a nice way to map what is in the
> configuration to the code paths, and implementations used within Joshua. It
> also would go a long way to allowing us to integrate unit tests throughout
> all the important classes in Joshua. What does everyone think? Would IoC be
> a good pattern to adopt? Is everyone ok with using guice (versus say some
> other IoC library).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
