Jerry Jensen writes:
> >> On 2/3/13 3:08 PM, Mark Wieder wrote:
> > Yeah, interesting point. I'm not sure what EOF means in that case
> > either. Is that "I received an EOF char from the port"?
>
> I don't think EOF is meaningful with a serial driver. The closest character is
Ctrl-D, EOT, end of
On Feb 3, 2013, at 2:49 PM, Mark Wieder wrote:
> Jacque-
>
> Sunday, February 3, 2013, 1:51:24 PM, you wrote:
>
>> On 2/3/13 3:08 PM, Mark Wieder wrote:
>>> Jacque-
>>>
>>> Sunday, February 3, 2013, 12:40:43 PM, you wrote:
>>>
In the case of sockets and drivers it is possible to read wit
Jacque-
Sunday, February 3, 2013, 1:51:24 PM, you wrote:
> On 2/3/13 3:08 PM, Mark Wieder wrote:
>> Jacque-
>>
>> Sunday, February 3, 2013, 12:40:43 PM, you wrote:
>>
>>> In the case of sockets and drivers it is possible to read without error
>>> but not receive all the data due to communication
On 2/3/13 3:08 PM, Mark Wieder wrote:
Jacque-
Sunday, February 3, 2013, 12:40:43 PM, you wrote:
In the case of sockets and drivers it is possible to read without error
but not receive all the data due to communication issues. In that case
you'd want to know if the read had paused or had really
Jacque-
Sunday, February 3, 2013, 12:40:43 PM, you wrote:
> In the case of sockets and drivers it is possible to read without error
> but not receive all the data due to communication issues. In that case
> you'd want to know if the read had paused or had really finished.
I was about to post the
Once again, Jacque puts the kibosh on our "it's a bug!" session by injecting
facts! You can't have any fun around here anymore. ;-)
Bob
On Feb 3, 2013, at 12:40 PM, J. Landman Gay wrote:
> On 2/3/13 1:08 PM, Richard Gaskin wrote:
>
>> Can you think of a circumstance in which you've already s
On 2/3/13 1:08 PM, Richard Gaskin wrote:
Can you think of a circumstance in which you've already specified to
read until EOF, and the command executes flawlessly just as you've asked
it to, yet you still need to be notified that it reached EOF?
The "read from file" command is a subset of the g
I ran into this a few weeks ago when I was having problems reading a file.
Turned out it was because I should have been doing a binary read, but
seeing EOF in the result made me think I'd run into some sort of error like
an unexpected EOF or something - wasted a couple of hours trying to track
tha
I think one of my guesses would have actually made more sense. Have the result
return the number of characters read. That way you could check for zero in the
result, and if not, you have the size of your chunk ready to go. But EOF in the
result is surprising. It's hard to imagine the developer l
On 04/02/2013, at 6:08 AM, Richard Gaskin wrote:
> Can you think of a circumstance in which you've already specified to read
> until EOF, and the command executes flawlessly just as you've asked it to,
> yet you still need to be notified that it reached EOF?
No
--
Monte Goulding
M E R Gould
Jerry Jensen wrote:
>>> On 03/02/2013, at 11:36 AM, Richard Gaskin wrote:
>>>
Without looking in the Dictionary, what would you expect the value
of tResult to be after successful execution of:
open file tValidFilePath for read
read from file tValidFilePath until EOF
I had a vague memory of this and checked in an old script and found the
following:
read from file laFile[pUrl] for 4096
if the result <> empty and the result <> "eof" then
...
Dave
On 3 Feb 2013, at 00:36, Richard Gaskin wrote:
> Without looking in the Dictionary, what would you expect the v
Wait... the number of characters read?
On Feb 2, 2013, at 4:36 PM, Richard Gaskin wrote:
> Without looking in the Dictionary, what would you expect the value of tResult
> to be after successful execution of:
>
> open file tValidFilePath for read
> read from file tValidFilePath until EOF
> put t
empty
On Feb 2, 2013, at 4:36 PM, Richard Gaskin wrote:
> Without looking in the Dictionary, what would you expect the value of tResult
> to be after successful execution of:
>
> open file tValidFilePath for read
> read from file tValidFilePath until EOF
> put the result into tResult
> close fi
EOF
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
Use Color Converter to convert CMYK, RGB, RAL, XYZ, H.Lab and other colour
spaces. http://www.color-converter.
Me too. ;-(
On Feb 2, 2013, at 4:39 PM, Monte Goulding wrote:
> :-(
>
> On 03/02/2013, at 11:38 AM, Monte Goulding
> wrote:
>
>> empty?
>>
>> On 03/02/2013, at 11:36 AM, Richard Gaskin
>> wrote:
>>
>>> Without looking in the Dictionary, what would you expect the value of
>>> tResult to
Me too. empty?
.Jerry
On Feb 2, 2013, at 4:38 PM, Monte Goulding wrote:
> empty?
>
> On 03/02/2013, at 11:36 AM, Richard Gaskin wrote:
>
>> Without looking in the Dictionary, what would you expect the value of
>> tResult to be after successful execution of:
>>
>> open file tValidFilePath fo
:-(
On 03/02/2013, at 11:38 AM, Monte Goulding wrote:
> empty?
>
> On 03/02/2013, at 11:36 AM, Richard Gaskin wrote:
>
>> Without looking in the Dictionary, what would you expect the value of
>> tResult to be after successful execution of:
>>
>> open file tValidFilePath for read
>> read fro
empty?
On 03/02/2013, at 11:36 AM, Richard Gaskin wrote:
> Without looking in the Dictionary, what would you expect the value of tResult
> to be after successful execution of:
>
> open file tValidFilePath for read
> read from file tValidFilePath until EOF
> put the result into tResult
> close
Without looking in the Dictionary, what would you expect the value of
tResult to be after successful execution of:
open file tValidFilePath for read
read from file tValidFilePath until EOF
put the result into tResult
close file tValidFilePath
--
Richard Gaskin
Fourth World
LiveCode training
20 matches
Mail list logo
