<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 06.10.2010, at 10:18, Philippe Marschall wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>2010/10/6 Norbert Hartl <<a href="mailto:norbert@hartl.name">norbert@hartl.name</a>>:<br><blockquote type="cite"><br></blockquote><blockquote type="cite">On 06.10.2010, at 08:56, Philippe Marschall wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">2010/10/5 Norbert Hartl <<a href="mailto:norbert@hartl.name">norbert@hartl.name</a>>:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I would like to have implemented<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">GRCodecStream>>isStream<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> ^ true<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">isStream is implemented at least in Object to return false. We some trouble using grease streams with the xml parser.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I also thought about this one once. The trouble is that we don't<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">implement the full stream protocol so you might end up wrapping them<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">again. OTOH it can't be more broken than it currently is.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I think there is difference between incomplete and broken ;) I mean if you start implementing a class that has stream in its name and that implements the same methods it only makes sense if most of the protocol is there, right? Or to say it in other words. If this is the case there will always be people like me asking why this and that isn't available.<br></blockquote><blockquote type="cite">I asked about Stream>>tab a while ago. Last time I just changed the code not to use Stream>>tab instead of putting tab into grease stream. The question about isStream is more easy to tackle. The question is what would be the replacement/workaround for isStream? I don't see a good one.<br></blockquote><br>Implement a wrapper around GRCodecStream that has the full stream<br>protocol. But I guess at one point or another we'll need to add more<br>of the stream protocol anyway so we can as well start now.<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><br></div><div>I wouldn't implement a wrapper around GRCodecStream I would replace it for my purpose. And that is probably not one of the goals of grease. The only thing I need to do is to read a XML file in a platform independent manner. This doesn't work with grease and that is a pitty. I don't even recognize the need for discussing this thoroughly. I'm just doing it because I don't have commit rights in the repo.</div><div>So it would be nice to hear something definite from the core developers. If you are willing to add this to grease that would be fine.</div><div><br></div><div>Waiting for judgement,</div><div><br></div><div>Norbert</div><div> </div><br></body></html>