'tags.e - current_tag()' ignores 'include_args' parameter

[hs2]

@SlickTeam: I think adding this parameter to the public interface was/is a good idea.
Would be nice if the parameter gets really used there
Thanks,
HS2

[Dennis]

This will be fixed in v13, however, as you might notice, we don't use current_tag() very much anymore, it's sort of a legacy function.  Generally, the modern way is to use tag_current_context() and tag_get_context_info() to get the data about the current symbol under the cursor.

[hs2]

Thanks Dennis !
Right - the new API is much more powerful and I already used somewhere else.
BTW: Is there a rule when to _UpdateContext first ? Since I had some problems with the context being not in sync I'm using it probably way too often now. Is it expensive to use it ? I had the impression that's it's quite fast...
However, If there is a bit more time I'll convert my legacy stuff using legacy API to the new interfaces...

HS2

[Dennis]

_UpdateContext() will force the entire file to be parsed (which really doesn't take that long) when the tagging information is out of date, but if it is already cached, _UpdateContext() is nearly instantaneous.

For example:

Code: [Select]

_UpdateContext(true);
_UpdateContext(true);
_UpdateContext(true);
_UpdateContext(true);
_UpdateContext(true);
_UpdateContext(true);
is for all practical purposes just as fast as:

Code: [Select]

_UpdateContext(true);

[hs2]

Ah - thanks. I assume that 'out-of-date' doesn't mean that just the file date is considered by the caching strategy.
In other words it also takes care about modified buffers (flagged by p_LastModified ?), right ?
HS2

[Dennis]

Yes, p_LastModified calls all the shots.  _UpdateContext() doesn't care about the file date, just whether the file's contents have or have not been modified since the last time _UpdateContext() was called.

In earlier versions of SlickEdit (v11 and lower), there was just one "context", so when you flipped between buffers, SlickEdit frequently reparsed files.  In v12, we have a working set of "contexts" corresponding to the most recently used files.  I chose to use a working set strategy instead of simply using one "context" per open file because (a) I don't have to track open files, (b) it limits memory consumption, and (c) the cache still works when you close a file and re-open it (references frequently does this when it is doing symbol analysis).  It really was a significant performance improvement, but nobody really noticed.

[jbhurst]

It really was a significant performance improvement, but nobody really noticed.

Aw Dennis, don't you think we all appreciate your talents???  We do!!! :-)

John Hurst
Wellington, New Zealand

[hs2]

C'mon Dennis - I already told that a number of times
last time: 06-07-2007, 19:32:44: v12.02 announcement:

(I also had the impression that v12.02 is again a bit faster.)

In fact I still can't believe it that while really sophisticated features were added in the past, the speed is still at an astonishing high level. Some (improved) features are even faster now. So keep up the good work !

HS2