You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
I've been trying to follow the conversation on adding a length limit to input streams to support parsing non null-terminated strings.
I see there are a few issues and even pull requests (most of them several years old) discussing the concept, and I see some support for it was finally added to master for the Parse() interface.
However.. nothing of the sort was ever done for ParseInSitu(), so the obvious question is why?
At my studio, we're mainly interested in doing insitu parsing for efficiency, so we really need support for this for cases where we cannot control the format of the input string. I could ofc modify the source code and put something together (the most straightforward solution would seem to be to do something like 58d72c7).
But the question remains.. why support this for read-only parsing but not in situ parsing? Is there anything I'm missing here?
The text was updated successfully, but these errors were encountered:
n00bmind
changed the title
Still no insitu parsing with a for non null-terminated strings?
Still no insitu parsing for non null-terminated strings?
Jul 27, 2023
Hi.
I've been trying to follow the conversation on adding a length limit to input streams to support parsing non null-terminated strings.
I see there are a few issues and even pull requests (most of them several years old) discussing the concept, and I see some support for it was finally added to master for the
Parse()
interface.However.. nothing of the sort was ever done for
ParseInSitu()
, so the obvious question is why?At my studio, we're mainly interested in doing insitu parsing for efficiency, so we really need support for this for cases where we cannot control the format of the input string. I could ofc modify the source code and put something together (the most straightforward solution would seem to be to do something like 58d72c7).
But the question remains.. why support this for read-only parsing but not in situ parsing? Is there anything I'm missing here?
The text was updated successfully, but these errors were encountered: