search for: memofybuff

...le to do that step-by-step, we could for example introduce a static FileSystem pointer that is initialized with the default system file system on startup (I like being able to do baby-steps) 2. add methods to FileSystem to support opening MemoryBuffers; the path forward will be to move all calls to MemofyBuffer::get*File through the FileSystem interface, but again that can be handled incrementally 3. at that point we'd have enough stuff in FileSystem to rebase FileManager on top of it; once 1 and 2 are finished for clang/.* we'll be able to completely move the virtual file support over into a ni...

...y-step, we could for example introduce a static > FileSystem pointer that is initialized with the default system file > system on startup (I like being able to do baby-steps) > 2. add methods to FileSystem to support opening MemoryBuffers; the > path forward will be to move all calls to MemofyBuffer::get*File > through the FileSystem interface, but again that can be handled > incrementally > 3. at that point we'd have enough stuff in FileSystem to rebase > FileManager on top of it; once 1 and 2 are finished for clang/.* we'll > be able to completely move the virtual fi...

...for example introduce a static >> FileSystem pointer that is initialized with the default system file >> system on startup (I like being able to do baby-steps) >> 2. add methods to FileSystem to support opening MemoryBuffers; the >> path forward will be to move all calls to MemofyBuffer::get*File >> through the FileSystem interface, but again that can be handled >> incrementally >> 3. at that point we'd have enough stuff in FileSystem to rebase >> FileManager on top of it; once 1 and 2 are finished for clang/.* we'll >> be able to completely...

...roduce a static >>> FileSystem pointer that is initialized with the default system file >>> system on startup (I like being able to do baby-steps) >>> 2. add methods to FileSystem to support opening MemoryBuffers; the >>> path forward will be to move all calls to MemofyBuffer::get*File >>> through the FileSystem interface, but again that can be handled >>> incrementally >>> 3. at that point we'd have enough stuff in FileSystem to rebase >>> FileManager on top of it; once 1 and 2 are finished for clang/.* we'll >>> b...

...y-step, we could for example introduce a static > FileSystem pointer that is initialized with the default system file > system on startup (I like being able to do baby-steps) > 2. add methods to FileSystem to support opening MemoryBuffers; the > path forward will be to move all calls to MemofyBuffer::get*File > through the FileSystem interface, but again that can be handled > incrementally > 3. at that point we'd have enough stuff in FileSystem to rebase > FileManager on top of it; once 1 and 2 are finished for clang/.* we'll > be able to completely move the virtual fi...

...for example introduce a static >> FileSystem pointer that is initialized with the default system file >> system on startup (I like being able to do baby-steps) >> 2. add methods to FileSystem to support opening MemoryBuffers; the >> path forward will be to move all calls to MemofyBuffer::get*File >> through the FileSystem interface, but again that can be handled >> incrementally >> 3. at that point we'd have enough stuff in FileSystem to rebase >> FileManager on top of it; once 1 and 2 are finished for clang/.* we'll >> be able to completely...

...roduce a static >>> FileSystem pointer that is initialized with the default system file >>> system on startup (I like being able to do baby-steps) >>> 2. add methods to FileSystem to support opening MemoryBuffers; the >>> path forward will be to move all calls to MemofyBuffer::get*File >>> through the FileSystem interface, but again that can be handled >>> incrementally >>> 3. at that point we'd have enough stuff in FileSystem to rebase >>> FileManager on top of it; once 1 and 2 are finished for clang/.* we'll >>> b...

...>>>> FileSystem pointer that is initialized with the default system file >>>> system on startup (I like being able to do baby-steps) >>>> 2. add methods to FileSystem to support opening MemoryBuffers; the >>>> path forward will be to move all calls to MemofyBuffer::get*File >>>> through the FileSystem interface, but again that can be handled >>>> incrementally >>>> 3. at that point we'd have enough stuff in FileSystem to rebase >>>> FileManager on top of it; once 1 and 2 are finished for clang/.* we'l...

...>>> FileSystem pointer that is initialized with the default system file > >>> system on startup (I like being able to do baby-steps) > >>> 2. add methods to FileSystem to support opening MemoryBuffers; the > >>> path forward will be to move all calls to MemofyBuffer::get*File > >>> through the FileSystem interface, but again that can be handled > >>> incrementally > >>> 3. at that point we'd have enough stuff in FileSystem to rebase > >>> FileManager on top of it; once 1 and 2 are finished for clang/.* we...

Hi Manuel, On Nov 28, 2011, at 2:49 AM, Manuel Klimek wrote: > Hi, > > while working on tooling on top of clang/llvm we found the file system > abstractions in clang/llvm to be one of the points that could be nicer > to integrate with. I’m writing this mail to propose a strawman and get > some feedback on what you guys think the right way forward is (or > whether we should

Hi, while working on tooling on top of clang/llvm we found the file system abstractions in clang/llvm to be one of the points that could be nicer to integrate with. I’m writing this mail to propose a strawman and get some feedback on what you guys think the right way forward is (or whether we should just leave things as they are). First, the FileManager we have in clang has helped us a lot for