Talk:cpp/io/c/fscanf
From cppreference.com
Mentioning time complexity of sscanf
There has been some blogging and discussion recently, about how sscanf can cause accidental quadratic performance ([1] [2] [3] [4]). Is that something that could/should be mentioned here? --Rchard2scout (talk) 02:05, 3 March 2021 (PST)
Clarifying Conversion Behavior in fscanf
We should add the following paragraph (quote from the current C draft) or equivalent regarding conversion behavior in fscanf:
Unless assignment suppression was indicated by a
*, the result of the conversion is placed in the object pointed to by the first argument following theformatargument that has not already received a conversion result. If this object does not have an appropriate type, or if the result of the conversion cannot be represented in the object, the behavior is undefined.