Re: [Kaldi-developers] Rework option passing

[Daniel P. <dp...@gm...>]

Arnab--  there was a bit of a discussion about this in the early days of
Kaldi.  Some (e.g. Karel) felt that we should have some kind of
name-qualification for options.  But my feeling was it was more in the
spirit of what I had in mind with Kaldi, to keep things simple and try to
ensure that a single program never had more than one option with the same
name.  I kind of still think this is the right way to go.  In the
particular case you mention, it seems like the option should always have
the same value anyway, so it might be possible to make it so it sets both
to the same value.  Is there a situation where you envisage having both
those configs used?

I think there may already be code there to detect that you registered two
configs with the same name (it will crash in this situation).

Dan


On Wed, Feb 20, 2013 at 11:35 AM, Arnab Ghoshal <ar...@gm...> wrote:

> Hi all,
>
> I just realized that it is possible for options of multiple modules to
> clash, since there is no way to uniquely identify an option from a
> particular class. For example, TrainingGraphCompilerOptions and
> WordBoundaryInfoNewOpts both have a 'reorder' option, which means only one
> of the 'reorder' options will be used in an executable that uses both.
>
> While this particular problem is easy to fix, there is a deeper issue with
> option parsing that I am mentioning here in case someone has time to fix
> this. I couldn't figure out how to use the bug-tracker on souceforge.
>
> -Arnab
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Kaldi-developers mailing list
> Kal...@li...
> https://lists.sourceforge.net/lists/listinfo/kaldi-developers
>
>