[Seaside-dev] Issue 282 in seaside: ReadStream>>#'next' might give
an error when at end
codesite-noreply at google.com
codesite-noreply at google.com
Thu Jan 15 01:08:52 UTC 2009
Status: Accepted
Owner: WeybridgeWay
Labels: Type-Defect Priority-Medium Version-Seaside2.9
New issue 282 by WeybridgeWay: ReadStream>>#'next' might give an error when
at end
http://code.google.com/p/seaside/issues/detail?id=282
WACallbackTest>>#'testMapCallback' is failing in GemStone because in
WAMapCallback>>#'valueForField:' the code assumes that #'next' will return
nil if at end. According
to ANSI, the behavior is undefined when you send #'next' and there is
nothing more to return. We
are reluctant to change the behavior of GemStone's streams. Thus, the
particular sender under
consideration here needs to be changed. Shall I add an explicit #'atEnd'
check to #'valueForField:' or
shall I create a new method (#'seasideNext' or #'nextOrNil'?) to ReadStream
and then call it instead
of #'next'? -- James Foster
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
More information about the seaside-dev
mailing list