@Dave-Allured When you say "CF-controlled attributes", are you referring to any values they may have, or to values that are from controlled vocabularies? It is true that applications written in C or FORTRAN will require code changes to handle **`string`** because the API and what is returned for string attributes and variables is different from that for char attributes and variables. Would a warning about avoiding **`string`** for maximum compatibility be sufficient?
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/141#issuecomment-407475189
