Deprecate, warn and convert seems reasonable. But for how long ? As the number of automatic conversions OMPI supports has shown a tendency to increase, and as these conversions happen all over the code base, we might want to setup a well defined path to deprecation, what and when has been deprecated, for how long we intend to keep them or their conversion around and finally when they should be completely removed (or moved into a state where we warn but not convert).
George. On Wed, Apr 8, 2020 at 10:33 AM Jeff Squyres (jsquyres) via devel < devel@lists.open-mpi.org> wrote: > On Apr 8, 2020, at 9:51 AM, Ralph Castain via devel < > devel@lists.open-mpi.org> wrote: > > > > We have deprecated a number of cmd line options (e.g., bynode, npernode, > npersocket) - what do we want to do about their MPI_Info equivalents when > calling comm_spawn? > > > > Do I silently convert them? Should we output a deprecation warning? > Return an error? > > > We should probably do something similar to what happens on the command > line (i.e., warn and convert). > > -- > Jeff Squyres > jsquy...@cisco.com > >
