You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am receiving empty data from well formed YAML (at least according to http://yaml-online-parser.appspot.com/). I traced through the code and I believe there is a bug in the code when the optional NSError argument passed is not nil. This happens in:
If the error passed is not nil, then this test passes even if there is no actual parsing error. I believe the test should be:
if (*error) {
yaml_document_delete(&document);
}
(also note that the pattern is not faithful to the Cocoa NSError pattern where you should only look at the NSError if you diagnosed the occurrence of an error in some other way. A non-nil error is not necessarily a good test for error, as we could have warnings, non-fatal errors, recovered errors… Now of course, this is no big deal. You can diverge from Cocoa patterns if you like).
The text was updated successfully, but these errors were encountered:
I am receiving empty data from well formed YAML (at least according to http://yaml-online-parser.appspot.com/). I traced through the code and I believe there is a bug in the code when the optional NSError argument passed is not nil. This happens in:
Where you find this test:
If the error passed is not nil, then this test passes even if there is no actual parsing error. I believe the test should be:
(also note that the pattern is not faithful to the Cocoa NSError pattern where you should only look at the NSError if you diagnosed the occurrence of an error in some other way. A non-nil error is not necessarily a good test for error, as we could have warnings, non-fatal errors, recovered errors… Now of course, this is no big deal. You can diverge from Cocoa patterns if you like).
The text was updated successfully, but these errors were encountered: