[
https://issues.apache.org/jira/browse/MIME4J-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark updated MIME4J-241:
------------------------
Description:
Not sure what's the desired behavior, so I just wrote the test, not a fix to
the problemm per se. (especially the behavior after we have reached EOF, should
we returns -1 or 0 for zero reads there? and as a side note: is it permissible
to reset after reaching EOF or should any further action lead to a special
result/error? all of that should be tested/defined within the test unit.)
read(buf, 0, 0) returns -1 in the new test case, whereas it returns 0 in the
existing test case.
Maybe MIME4J-240 can be replaced by this report.
was:
Not sure what's the desired behavior, so I just wrote the test, not a fix to
the problemm per se. (especially the behavior after we have reached EOF, should
we returns -1 or 0 for zero reads there? and as a side note: is it permissible
to reset after reaching EOF or should any further action lead to a special
result/error?)
read(buf, 0, 0) returns -1 in the new test case, whereas it returns 0 in the
existing test case.
Maybe MIME4J-240 can be replaced by this report.
> inconsistent StringInputStream read zero behavior?
> --------------------------------------------------
>
> Key: MIME4J-241
> URL: https://issues.apache.org/jira/browse/MIME4J-241
> Project: James Mime4j
> Issue Type: Bug
> Components: dom
> Affects Versions: 0.7.2
> Reporter: Mark
> Priority: Critical
> Attachments: mime4j.2.patch
>
>
> Not sure what's the desired behavior, so I just wrote the test, not a fix to
> the problemm per se. (especially the behavior after we have reached EOF,
> should we returns -1 or 0 for zero reads there? and as a side note: is it
> permissible to reset after reaching EOF or should any further action lead to
> a special result/error? all of that should be tested/defined within the test
> unit.)
> read(buf, 0, 0) returns -1 in the new test case, whereas it returns 0 in the
> existing test case.
> Maybe MIME4J-240 can be replaced by this report.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
