Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359417 - [cache]make difference between removed file and dirty file
Summary: [cache]make difference between removed file and dirty file
Status: NEW
Alias: None
Product: DLTK
Classification: Technology
Component: Common (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: dltk.common-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-29 09:06 EDT by Simon Bernard CLA
Modified: 2011-09-29 09:32 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Bernard CLA 2011-09-29 09:06:37 EDT
In DLTK, there are a cache to store AST of a source file (to avoid to re-parse file each time we need to acces to the ast)

The ast is remove from cache when :
- file is modified
- file is remove from workspace (or builpath?)

This cache management don't allow to implement a behavior which could be cool for most of editor :  when editor is  not able to parse a file (because there are a syntax error for example), return the last valid AST  for this file.

currently, we can use the cache system of DLTK because when a file is modified, it's remove from cache. so we must create our own cache system to implement this.

A way to resolve this problem, is to :
- remove file from cache when it is removed from workspace(or buildpath).
- flag the file as dirty in the cache when the file is just modified.