Frank Kleine

In my last commit I updated the org layer to load the new classes. However, I'm a bit unsure how to continue: - Remove all classes/interfaces from org which don't...

> Merging any 2.x changes into 3.x could be fun... Yes, that's one of the thoughts I had - we might create a maintenance problem for us. So in case...

Over the weekend I thought a bit about this and came up with the following idea: 1. Merge the namespace change into 1.x. 2. Rename the classes that will receive...

If I remember correctly, within the plan I outlined above this should now be at point 3. Unfortunately for this PR I got pulled into a large project mid March...

I think that's something that could be improved in vfsStream. As operating system support multibyte characters in filenames, vfsStream should support this as well.

This would be an interesting feature, but implementing it the way you suggest would make the internals really complicated. Currently instances of `vfsStreamContent` just know their parent path, but for...

Thanks! I think we should merge this after #221 is finished, as it reduces the points where seek functionality exists back to one. The other question for me is whether...

> Alternative implementation that applies on top of #221: [refactor/rename_and_restructure...IMSoP:issue-222-rebase](https://github.com/bovigo/vfsStream/compare/refactor/rename_and_restructure...IMSoP:issue-222-rebase) > > Oddly, a bunch of the tests that my change caused to fail don't seem to exist on that...

> I think to backport to 1.x, we'd need to also backport #220 (otherwise the streams all have the same offset anyway), so it needs a call on the risk...

Basically by design: not intentional, but due to the limitations of user defined stream wrappers in PHP and the knowledge of the author when vfsStream was initially created*. You can...