![]() ![]() It will tell me the position where it crashed (1037), but I'm unable to get it to pick back up at this spot (the documentation on this in the textscan help is pretty weak- why is it a string?). I'm not sure what you mean by the dump tool. You might take a (short) snapshot of the the screen of one that worksĪnd one that fails and post it maybe somebody else's eyes will be W/O the actual data files it's pretty much a guess from here as to Of fopen() shouldn't matter, but you can always try it for grins. ![]() Which platform is/are being read on-Mac, I guess? There the 't' option No chance the ones that fail have something like that to distinguish them? I'm unable to tell from the original post-are these files both createdĪnd read on the same platform or is there a case of moving them across? Use the dump tool to then look specifically there and see if that does Output on a failure so one isn't totally flying blind so much as in _a_good_thing_ (tm) ) if textscan had some more informative diagnostic Precisely the failure occurred (BTW, TMW, it would surely be I'd use the optional return argument to see what did read and where, > character and I can't see any difference between files that work and I found Text Wrangler which allows me to view spaces and newline
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |