General information
Category:
Coding, syntax & commands
Title:
FGETS in SP4 -- a code breaker?
Take a look at the SP4 update notes for VFP. How many people have legacy VFP code out there, before the FileToStr function came along, that _knows_ it's going to reading an entire textblob file of some arbitrary length less than 32K characters and is simply coded as:
cMyStr=FGets(hFile,32767)
... Basically the equivalent functionality of FileToStr before it came along.
That apparently will now be broken. From the SP4 info:
FGETS function update
A minor behavior change was necessary for the FGETS() function related to Knowledge Base article.
The optional nBytes parameter now has a maximum value of 8192. By definition, FGETS() only returns bytes up to a carriage return if one is encountered before the parameter value is reached.
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only