dictionary deprecation mechanism quite verbose

I am getting (e.g. smallPoolFire2D tutorial)

keyword is deemed to be 5 months old

on all processors. One should be enough.

Yes, makes sense. I used std::cerr instead of Info, since this could fail while reading any dictionary.

Explicitly check UPstream::parRun?

I actually thought of Pstream::master() but just wanted to provide a quick explanation for why you are seeing so many complaints.

What do you think about the same treatment for the following as well? They are all places where we use a std::cerr instead of a Warning, since we need it to work before everything is constructed, but where we'd have happily had Warning with output on the master only.

• IOerror::SafeFatalIOError
• dictionary::excessTokens
• entry::getKeyword
• entry::New

Sure but is there an initialisation order problem?

myProcNo_[communicator] == masterNo();

myProcNo_ gets sized after e.g. etc/controlDict reading?

mentioned in commit 9f5a16357f0b6d90d070a3b5aac7d6a05050e0b1

closed

mentioned in issue #893 (closed)