[
Lists Home |
Date Index |
Thread Index
]
Tim Bray scripsit:
> genxText(genxWriter w, utf8Byte * start, utf8Byte * end)
I think the second argument should be one past the end. This makes
outputting things in chunks very easy: you just set start to end and
call it again with a new value of end. Computing the length from
the end or vice versa is also not subject to fencepost errors.
> - if you have a zero byte in the string before you get to the end mark,
> should it just stop, or throw an error? The first is more consistent
> with C culture (cf strncpy) but the latter a bit more stringent.
> Moderately leaning to just stopping.
+1
> - if the stop marker is stupidly in the middle of a UTF-8 character,
> genx should detect this and declare an error. The existence of this
> situation is the only good argument for a count rather than a stopper.
> But not quite good enough. -Tim
+1
--
John Cowan jcowan@reutershealth.com www.reutershealth.com www.ccil.org/~cowan
The known is finite, the unknown infinite; intellectually we stand
on an islet in the midst of an illimitable ocean of inexplicability.
Our business in every generation is to reclaim a little more land,
to add something to the extent and the solidity of our possessions.
--Thomas Henry Huxley
|
