Thanks!!! On Thu, Feb 19, 2015 at 11:58 AM, Ralph Castain <r...@open-mpi.org> wrote:
> We call it a “synonym” - but yes, you certainly can, and we do it in many > places. From mca_base_var.h: > > /** > * Register a synonym name for an MCA variable. > * > * @param[in] synonym_for The index of the original variable. This index > * must not refer to a synonym. > * @param[in] project_name The project this synonym belongs to. Should > * not be NULL (except for legacy reasons). > * @param[in] framework_name The framework this synonym belongs to. > * @param[in] component_name The component this synonym belongs to. > * @param[in] synonym_name The synonym name. > * @param[in] flags Flags for this synonym. > * > * @returns index Variable index for new synonym on success. > * @returns OPAL_ERR_BAD_VAR If synonym_for does not reference a valid > * variable. > * @returns OPAL_ERR_OUT_OF_RESOURCE If memory could not be allocated. > * @returns OPAL_ERROR For all other errors. > * > * Upon success, this function creates a synonym MCA variable > * that will be treated almost exactly like the original. The > * type (int or string) is irrelevant; this function simply > * creates a new name that by which the same variable value is > * accessible. > * > * Note that the original variable name has precendence over all > * synonyms. For example, consider the case if variable is > * originally registered under the name "A" and is later > * registered with synonyms "B" and "C". If the user sets values > * for both MCA variable names "A" and "B", the value associated > * with the "A" name will be used and the value associated with > * the "B" will be ignored (and will not even be visible by the > * mca_base_var_*() API). If the user sets values for both MCA > * variable names "B" and "C" (and does *not* set a value for > * "A"), it is undefined as to which value will be used. > */ > OPAL_DECLSPEC int mca_base_var_register_synonym (int synonym_for, const > char *project_name, > const char > *framework_name, > const char > *component_name, > const char *synonym_name, > mca_base_var_syn_flag_t > flags); > > > On Feb 19, 2015, at 8:54 AM, Joshua Ladd <jladd.m...@gmail.com> wrote: > > Folks, > > Is it possible to define an alias for an MCA parameter? Grepping around > the interwebs, it seems there was an RFC along these lines in 2008. > > http://www.open-mpi.org/community/lists/devel/2008/04/3613.php > > It doesn't appear that the functionality was added or, if it was, it has > since been removed. > > Thanks, > > Josh > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/02/16995.php > > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/02/16996.php >
