<br><br><div><span class="gmail_quote">On 6/5/05, <b class="gmail_sendername">holger krekel</b> <<a href="mailto:hpk@trillke.net">hpk@trillke.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sun, Jun 05, 2005 at 12:13 -0700, Narayan Newton wrote:<br>> As for the inheritance, I was thinking that there would be some methods that<br>> every FS class should have, but are more convenience methods and would
<br>> pretty much just be wrappers around other class methods.<br><br>Maybe. IMO it makes sense to keep the lowlevel filesystem<br>class/API _very_ minimal and with no fluff so that it is easy to<br>implement a new backend. You might be suprised how difficult it is
<br>to implement and test common semantics of just a few filesystem<br>implementations especially when it comes to clean error<br>conditions/uniform exception handling.<br><br>> It would be nice to not have to write this for every FS
<br>> class, just inherit them from the parent.<br><br>Sure enough. However, Filename and/or URI manipulations<br>should probably go at a separated layer (call it 'frontend' if<br>you like) that can make use of filesystem implementations
<br>without a need to subclass.<br><br>cheers,<br><br> holger<br></blockquote></div><br>Agreed. I had misinterpreted what you said. :)<br>
<br><br>-- <br>Narayan Newton