lxr-developer Mailing List for LXR Cross Referencer (Page 15)
Brought to you by:
ajlittoz
Menu
▾
▴
lxr-developer — Don't use, active developers only
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(11) |
Jun
(21) |
Jul
(14) |
Aug
(83) |
Sep
(23) |
Oct
(37) |
Nov
(52) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(28) |
Feb
(40) |
Mar
(21) |
Apr
(8) |
May
(21) |
Jun
(13) |
Jul
(9) |
Aug
(5) |
Sep
(8) |
Oct
(7) |
Nov
(2) |
Dec
|
| 2003 |
Jan
(2) |
Feb
(1) |
Mar
(11) |
Apr
(4) |
May
(6) |
Jun
(15) |
Jul
(4) |
Aug
(4) |
Sep
(9) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2004 |
Jan
(4) |
Feb
|
Mar
(4) |
Apr
(12) |
May
(5) |
Jun
(9) |
Jul
(47) |
Aug
(1) |
Sep
(1) |
Oct
(7) |
Nov
|
Dec
(1) |
| 2005 |
Jan
(4) |
Feb
(2) |
Mar
(3) |
Apr
(10) |
May
(9) |
Jun
(15) |
Jul
(3) |
Aug
(1) |
Sep
(8) |
Oct
(9) |
Nov
(10) |
Dec
(4) |
| 2006 |
Jan
(1) |
Feb
|
Mar
(9) |
Apr
(5) |
May
(1) |
Jun
(6) |
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(2) |
Nov
|
Dec
(3) |
| 2007 |
Jan
(2) |
Feb
(1) |
Mar
(32) |
Apr
(3) |
May
(3) |
Jun
(16) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(4) |
Dec
(3) |
| 2008 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(46) |
Apr
(70) |
May
(15) |
Jun
(13) |
Jul
(1) |
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
(5) |
Feb
(4) |
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(7) |
Nov
(6) |
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
(85) |
Apr
(18) |
May
(4) |
Jun
(3) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(2) |
Dec
(20) |
| 2012 |
Jan
(17) |
Feb
(16) |
Mar
(13) |
Apr
(18) |
May
|
Jun
(6) |
Jul
(6) |
Aug
(10) |
Sep
(15) |
Oct
(10) |
Nov
(25) |
Dec
(1) |
|
From: Malcolm B. <mal...@gm...> - 2009-04-22 11:55:43
|
Hi Adrian, Did your recent Oracle patches include/supersede the patches in bug 1085321 - https://sourceforge.net/tracker/?func=detail&aid=1085321&group_id=27350&atid=390117 ? If so could you close the bug? Cheers, Malcolm |
|
From: SourceForge.net <no...@so...> - 2009-04-22 11:52:40
|
Bugs item #469413, was opened at 2001-10-09 06:38 Message generated for change (Settings changed) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=469413&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database interface Group: current cvs Status: Open Resolution: None Priority: 3 Private: No Submitted By: Malcolm Box (mbox) >Assigned to: AdrianIssott (adrianissott) Summary: Non-symbols can be mistaken for symbols Initial Comment: When marking up source code, each possible string is checked to see if it is a symbol, by calling issymbol(). The implementations in Mysql.pm and Postgres.pm only use the string to lookup whether this is a symbol. Unfortunately it is possible that in one release a string is a symbol, while in another it is not. Since the release of the file being looked at is not taken into account, the current algorithm will highlight symbols that, when clicked on, will return "Not used". The solution is to change issymbol to do: select s.symid from symbols s, releases r, indexes i where s.symname = 'name' and i.symid = s.symid and i.fileid = r.fileid and r.release = 'release'; This is not much slower, and the results could be cached. Note that is problem shows up only rarely, since it is unusual to have a string that both resembles an identifier (not a reserved word, not a string/include token) but matches a symbol name in another release. The easiest way to show it up is to look at the source of a release that has not be indexed yet. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=469413&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-22 11:51:06
|
Feature Requests item #2755445, was opened at 2009-04-12 11:28 Message generated for change (Comment added) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2755445&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Interface Group: None Status: Open Priority: 7 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: Language Specific Searches Initial Comment: The identifier search page doesn't allow language-specific searching. This would be updated as follows: 1) Users are given the option to restrict their search to specific programming languages via a series of check boxes. By default all languages will be selected for searching. 2) The list of programming languages shown will be auto-generated to be just those listed in the LXR index. When source files are being shown by LXR all text that matches a symbol in the LXR index are shown as links to an identifier search for that symbol. This would be updated as follows: 3) Only symbols in the same programming language as the file itself would be shown as identifier search links. Any text matching symbols in other programming languages would not be treated as symbols. 4) The symbol links would be restricted to identifier searches of just symbols of the same programming language. NB the user could then easily add other languages to the search as per sub-feature (1). ---------------------------------------------------------------------- >Comment By: Malcolm Box (mbox) Date: 2009-04-22 12:51 Message: Would also be good to fix this bug https://sourceforge.net/tracker/?func=detail&aid=469413&group_id=27350&atid=390117 (identifier checking doesn't take account of release) at the same time if you're making changes in this area. ---------------------------------------------------------------------- Comment By: AdrianIssott (adrianissott) Date: 2009-04-21 20:27 Message: Malcolm has requested the sub-features (3) and (4) be configurable. Potentially a good way to do this would be to do this using the filetype section of lxr.conf and hence specify the configurablility per file type. ---------------------------------------------------------------------- Comment By: AdrianIssott (adrianissott) Date: 2009-04-12 11:33 Message: This feature would be a little easier to do if Feature Request 1691378 (Rearchitect the DB backends) was done first. See https://sourceforge.net/tracker/?func=detail&aid=1691378&group_id=27350&atid=390120. ---------------------------------------------------------------------- Comment By: AdrianIssott (adrianissott) Date: 2009-04-12 11:31 Message: Additional sub-feature: 5) The general search page doesn't allow language-specific searching. This would be updated in exactly the same way as described for the identifier search pages in sub-features (1) and (2). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2755445&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-21 19:27:21
|
Feature Requests item #2755445, was opened at 2009-04-12 11:28 Message generated for change (Comment added) made by adrianissott You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2755445&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Interface Group: None Status: Open Priority: 7 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: Language Specific Searches Initial Comment: The identifier search page doesn't allow language-specific searching. This would be updated as follows: 1) Users are given the option to restrict their search to specific programming languages via a series of check boxes. By default all languages will be selected for searching. 2) The list of programming languages shown will be auto-generated to be just those listed in the LXR index. When source files are being shown by LXR all text that matches a symbol in the LXR index are shown as links to an identifier search for that symbol. This would be updated as follows: 3) Only symbols in the same programming language as the file itself would be shown as identifier search links. Any text matching symbols in other programming languages would not be treated as symbols. 4) The symbol links would be restricted to identifier searches of just symbols of the same programming language. NB the user could then easily add other languages to the search as per sub-feature (1). ---------------------------------------------------------------------- >Comment By: AdrianIssott (adrianissott) Date: 2009-04-21 20:27 Message: Malcolm has requested the sub-features (3) and (4) be configurable. Potentially a good way to do this would be to do this using the filetype section of lxr.conf and hence specify the configurablility per file type. ---------------------------------------------------------------------- Comment By: AdrianIssott (adrianissott) Date: 2009-04-12 11:33 Message: This feature would be a little easier to do if Feature Request 1691378 (Rearchitect the DB backends) was done first. See https://sourceforge.net/tracker/?func=detail&aid=1691378&group_id=27350&atid=390120. ---------------------------------------------------------------------- Comment By: AdrianIssott (adrianissott) Date: 2009-04-12 11:31 Message: Additional sub-feature: 5) The general search page doesn't allow language-specific searching. This would be updated in exactly the same way as described for the identifier search pages in sub-features (1) and (2). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2755445&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-21 19:12:55
|
Bugs item #2752574, was opened at 2009-04-11 11:24 Message generated for change (Comment added) made by adrianissott You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2752574&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: v0.9.6 >Status: Closed >Resolution: Fixed Priority: 6 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: The LXR general text search doesn't work with Swish on Windo Initial Comment: Performing a general text search for any thing at all when using Swish and a webserver on Windows results in output such as the attached "broken_search.html". ---------------------------------------------------------------------- >Comment By: AdrianIssott (adrianissott) Date: 2009-04-21 20:12 Message: Fix tested on both windows and unix ---------------------------------------------------------------------- Comment By: AdrianIssott (adrianissott) Date: 2009-04-11 11:28 Message: What seems to be happening is that the output of swish is being shown directly in the HTML and not being formatted by the search script. I've attached a patch that avoids complicated use of pipes that works on windows. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2752574&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-21 14:40:25
|
Feature Requests item #2774495, was opened at 2009-04-19 16:55 Message generated for change (Comment added) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None Status: Open Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: Deprecate or Remove Unused LXR::Lang Modules Initial Comment: The following LXR::Lang modules don't actually get used by default: * LXR::Lang::Perl (last modified in CVS in Mar 2001) * LXR::Lang::Python (last modified in CVS in Sept 1999) Instead LXR::Lang::Generic is used for Perl and Python. Having the above modules present is just confusing and hence should be deprecated or removed. ---------------------------------------------------------------------- >Comment By: Malcolm Box (mbox) Date: 2009-04-21 15:40 Message: I say nuke the Lang modules. Don't know whether the DB module works or not - I'll give it a test to see. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-20 20:30 Message: One other thought - is anyone actually using LXR::Index::DB? I'm not sure it'll run since it too hasn't been changed in ages. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-20 20:29 Message: So would you like me to delete them rather than some kind of deprecation? I must admit I'd prefer to get rid of them entirely since I'd be surprised if anyone is actually using them. As for alternatives to using LXR::Lang::Generic, Cobol and Java would be the only remaining two that are different and both derive from LXR::Lang::Generic. This would then leave the question of why have both LXR::Lang and LXR::Lang::Generic but that's a bigger question ... ---------------------------------------------------------------------- Comment By: Malcolm Box (mbox) Date: 2009-04-20 10:18 Message: Agreed, they should go. It is useful to have at least one language module as an example of how to create one - I think the Cobol one is still used, so that would serve. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-21 11:19:40
|
Bugs item #2777352, was opened at 2009-04-21 12:19 Message generated for change (Tracker Item Submitted) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2777352&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: current cvs Status: Open Resolution: None Priority: 5 Private: No Submitted By: Malcolm Box (mbox) Assigned to: AdrianIssott (adrianissott) Summary: No install instructions for Windows Initial Comment: The current install instructions don't cover installation on windows, even though LXR is supposed to work on Windows. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2777352&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-20 19:30:58
|
Feature Requests item #2774495, was opened at 2009-04-19 15:55 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None Status: Open Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: Deprecate or Remove Unused LXR::Lang Modules Initial Comment: The following LXR::Lang modules don't actually get used by default: * LXR::Lang::Perl (last modified in CVS in Mar 2001) * LXR::Lang::Python (last modified in CVS in Sept 1999) Instead LXR::Lang::Generic is used for Perl and Python. Having the above modules present is just confusing and hence should be deprecated or removed. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-20 19:30 Message: One other thought - is anyone actually using LXR::Index::DB? I'm not sure it'll run since it too hasn't been changed in ages. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-20 19:29 Message: So would you like me to delete them rather than some kind of deprecation? I must admit I'd prefer to get rid of them entirely since I'd be surprised if anyone is actually using them. As for alternatives to using LXR::Lang::Generic, Cobol and Java would be the only remaining two that are different and both derive from LXR::Lang::Generic. This would then leave the question of why have both LXR::Lang and LXR::Lang::Generic but that's a bigger question ... ---------------------------------------------------------------------- Comment By: Malcolm Box (mbox) Date: 2009-04-20 09:18 Message: Agreed, they should go. It is useful to have at least one language module as an example of how to create one - I think the Cobol one is still used, so that would serve. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-20 19:29:53
|
Feature Requests item #2774495, was opened at 2009-04-19 15:55 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None Status: Open Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: Deprecate or Remove Unused LXR::Lang Modules Initial Comment: The following LXR::Lang modules don't actually get used by default: * LXR::Lang::Perl (last modified in CVS in Mar 2001) * LXR::Lang::Python (last modified in CVS in Sept 1999) Instead LXR::Lang::Generic is used for Perl and Python. Having the above modules present is just confusing and hence should be deprecated or removed. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-20 19:29 Message: So would you like me to delete them rather than some kind of deprecation? I must admit I'd prefer to get rid of them entirely since I'd be surprised if anyone is actually using them. As for alternatives to using LXR::Lang::Generic, Cobol and Java would be the only remaining two that are different and both derive from LXR::Lang::Generic. This would then leave the question of why have both LXR::Lang and LXR::Lang::Generic but that's a bigger question ... ---------------------------------------------------------------------- Comment By: Malcolm Box (mbox) Date: 2009-04-20 09:18 Message: Agreed, they should go. It is useful to have at least one language module as an example of how to create one - I think the Cobol one is still used, so that would serve. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-20 09:37:44
|
Feature Requests item #2774495, was opened at 2009-04-19 16:55 Message generated for change (Settings changed) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None Status: Open Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) >Assigned to: AdrianIssott (adrianissott) Summary: Deprecate or Remove Unused LXR::Lang Modules Initial Comment: The following LXR::Lang modules don't actually get used by default: * LXR::Lang::Perl (last modified in CVS in Mar 2001) * LXR::Lang::Python (last modified in CVS in Sept 1999) Instead LXR::Lang::Generic is used for Perl and Python. Having the above modules present is just confusing and hence should be deprecated or removed. ---------------------------------------------------------------------- Comment By: Malcolm Box (mbox) Date: 2009-04-20 10:18 Message: Agreed, they should go. It is useful to have at least one language module as an example of how to create one - I think the Cobol one is still used, so that would serve. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 |
|
From: Malcolm B. <mal...@gm...> - 2009-04-20 09:24:02
|
On Sun, Apr 19, 2009 at 9:58 AM, Adrian Issott <adr...@ho...> wrote: > Hi Malcolm, > > To give you some additional background on my change, I saw the line "$root = > "/Users/malcolmbox/dev/lxr-src/";" in tests\PlainTest.pm and assumed that > this was something on your local machine that hadn't been submitted to CVS. Yes it was/is - shows that I've been the only person running these tests I guess! > Anyhow, I'm happy to move the test-scr folder (or whatever you were using > originally) into the lxr-tools module provided we update the tests to check > the test src folder is actually present and die if it isn't. I think that's a good plan - there are various other test files in there already to test for some previous bugs (e.g. filenames with spaces, directories containing directories of same name etc). > I'm not sure about moving the test scripts themselves - we don't want to > give people the impression there are no tests but then the scripts should > really be in the same module as the test src so they are keep in sync. I > know - how about we move everything to do with testing into the lxr-tools > module and just leave a note in the current test dir in the lxr module > saying how to get the tests? Good plan - there's a readme in the test directory that is a perfect place for that. Also the makerelease.pl script in lxr-tools will need updating as it calls the tests. Malcolm > >> From: mal...@gm... >> Date: Fri, 17 Apr 2009 11:29:11 +0100 >> To: lxr...@li... >> Subject: Re: [Lxr-dev] [Lxr-commits] CVS: lxr/tests/test-src - New >> directory >> >> Hi Adrian, >> >> I've been moving directories/files for testing to the lxr-tools module >> in the test-data directory - it looks like this commit is adding some >> test files into the main lxr module. >> >> The main reason for this is to separate out the development >> infrastructure from the released code - although I haven't moved the >> actual test code yet (perhaps this would be worth doing). >> >> How do you feel about moving this across to the lxr-tools module? >> >> Cheers, >> >> Malcolm >> >> On Fri, Apr 10, 2009 at 9:29 PM, AdrianIssott >> <adr...@us...> wrote: >> > Update of /cvsroot/lxr/lxr/tests/test-src >> > In directory >> > ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv10674/tests/test-src >> > >> > Log Message: >> > Directory /cvsroot/lxr/lxr/tests/test-src added to the repository >> > >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > Stay on top of everything new and different, both inside and >> > around Java (TM) technology - register by April 22, and save >> > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. >> > 300 plus technical and hands-on sessions. Register today. >> > Use priority code J9JMT32. http://p.sf.net/sfu/p >> > _______________________________________________ >> > Lxr-commits mailing list >> > Lxr...@li... >> > https://lists.sourceforge.net/lists/listinfo/lxr-commits >> > >> >> >> ------------------------------------------------------------------------------ >> Stay on top of everything new and different, both inside and >> around Java (TM) technology - register by April 22, and save >> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. >> 300 plus technical and hands-on sessions. Register today. >> Use priority code J9JMT32. http://p.sf.net/sfu/p >> _______________________________________________ >> Lxr-developer mailing list >> Lxr...@li... >> https://lists.sourceforge.net/lists/listinfo/lxr-developer > > ________________________________ > Windows Live Messenger just got better. Find out more! |
|
From: SourceForge.net <no...@so...> - 2009-04-20 09:18:16
|
Feature Requests item #2774495, was opened at 2009-04-19 16:55 Message generated for change (Comment added) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None Status: Open Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: Nobody/Anonymous (nobody) Summary: Deprecate or Remove Unused LXR::Lang Modules Initial Comment: The following LXR::Lang modules don't actually get used by default: * LXR::Lang::Perl (last modified in CVS in Mar 2001) * LXR::Lang::Python (last modified in CVS in Sept 1999) Instead LXR::Lang::Generic is used for Perl and Python. Having the above modules present is just confusing and hence should be deprecated or removed. ---------------------------------------------------------------------- >Comment By: Malcolm Box (mbox) Date: 2009-04-20 10:18 Message: Agreed, they should go. It is useful to have at least one language module as an example of how to create one - I think the Cobol one is still used, so that would serve. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-19 15:55:14
|
Feature Requests item #2774495, was opened at 2009-04-19 16:55 Message generated for change (Tracker Item Submitted) made by adrianissott You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None Status: Open Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: Nobody/Anonymous (nobody) Summary: Deprecate or Remove Unused LXR::Lang Modules Initial Comment: The following LXR::Lang modules don't actually get used by default: * LXR::Lang::Perl (last modified in CVS in Mar 2001) * LXR::Lang::Python (last modified in CVS in Sept 1999) Instead LXR::Lang::Generic is used for Perl and Python. Having the above modules present is just confusing and hence should be deprecated or removed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2774495&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-19 10:18:24
|
Bugs item #2774061, was opened at 2009-04-19 11:13 Message generated for change (Comment added) made by adrianissott You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2774061&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database interface Group: v0.9.6 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: Using PostGreSql Results in Malformed HTML in Ident Pages Initial Comment: Using PostGreSql v8.3 on Windows XP results in ident pages such as the one attached to the bug report. The issue is that Declarations are described such as: <td><a class='search-decl' href="/lxr/source/perl/f32overview.pl#215">/perl/f32overview.pl, line 215</a></td><td>subroutine but when I run exactly the same setup except that MySql has been substituted for PostGreSql I get lines such as <td><a class='search-decl' href="/lxr/source/perl/f32overview.pl#215">/perl/f32overview.pl, line 215</a></td><td>subroutine</td><td></td> ---------------------------------------------------------------------- >Comment By: AdrianIssott (adrianissott) Date: 2009-04-19 11:18 Message: The problem was that PostGreSql returned the type of a symbol with an extra space on the end (which hadn't been inserted into the db) so the LXR::Index::PostGreSql now removes trailing white space from a type when returning the index for a particular symbol ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2774061&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-19 10:13:25
|
Bugs item #2774061, was opened at 2009-04-19 11:13 Message generated for change (Tracker Item Submitted) made by adrianissott You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2774061&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database interface Group: v0.9.6 Status: Open Resolution: None Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: Using PostGreSql Results in Malformed HTML in Ident Pages Initial Comment: Using PostGreSql v8.3 on Windows XP results in ident pages such as the one attached to the bug report. The issue is that Declarations are described such as: <td><a class='search-decl' href="/lxr/source/perl/f32overview.pl#215">/perl/f32overview.pl, line 215</a></td><td>subroutine but when I run exactly the same setup except that MySql has been substituted for PostGreSql I get lines such as <td><a class='search-decl' href="/lxr/source/perl/f32overview.pl#215">/perl/f32overview.pl, line 215</a></td><td>subroutine</td><td></td> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2774061&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-19 09:52:06
|
Bugs item #2773982, was opened at 2009-04-19 10:23 Message generated for change (Comment added) made by adrianissott You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2773982&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: v0.9.6 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: Identifer Search Results Are Not Sorted When Shown Initial Comment: For instance a search for the "add_tracers" identifier might show the references as: /python/EntryExitTracerFile.py, line 89 /python/InsertTracePoints.py, line 176 or /python/InsertTracePoints.py, line 176 /python/EntryExitTracerFile.py, line 89 The same kind of issue occurs for declarations too. Fixing this issue will make finding the references or declarations easier for users browsing the lxr identifier search results. ---------------------------------------------------------------------- >Comment By: AdrianIssott (adrianissott) Date: 2009-04-19 10:52 Message: * MySql, Oracle and Postgres databases now sort the results in the same way. * Declarations are sorted by filename, line and then by type * References are sorted by filename and then by line ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2773982&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-19 09:23:22
|
Bugs item #2773982, was opened at 2009-04-19 10:23 Message generated for change (Tracker Item Submitted) made by adrianissott You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2773982&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: v0.9.6 Status: Open Resolution: None Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: Identifer Search Results Are Not Sorted When Shown Initial Comment: For instance a search for the "add_tracers" identifier might show the references as: /python/EntryExitTracerFile.py, line 89 /python/InsertTracePoints.py, line 176 or /python/InsertTracePoints.py, line 176 /python/EntryExitTracerFile.py, line 89 The same kind of issue occurs for declarations too. Fixing this issue will make finding the references or declarations easier for users browsing the lxr identifier search results. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2773982&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-19 09:17:34
|
Bugs item #2773972, was opened at 2009-04-19 10:14 Message generated for change (Comment added) made by adrianissott You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2773972&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database interface Group: v0.9.6 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: initdb-oracle.sql doesn't work with 10.2 of Oracle Express Initial Comment: See the attached file for the full output from running initdb-oracle.sql using sqlplus. The really suspicious bit is: SP2-0734: unknown command beginning "constraint..." - rest of line ignored. SP2-0042: unknown command ")" - rest of line ignored. create index lxr_i_indexes on lxr_indexes(symid) ---------------------------------------------------------------------- >Comment By: AdrianIssott (adrianissott) Date: 2009-04-19 10:17 Message: Changed invalid C++ style comment to be a SQL comment ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2773972&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-19 09:14:49
|
Bugs item #2773972, was opened at 2009-04-19 10:14 Message generated for change (Tracker Item Submitted) made by adrianissott You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2773972&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database interface Group: v0.9.6 Status: Open Resolution: None Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: initdb-oracle.sql doesn't work with 10.2 of Oracle Express Initial Comment: See the attached file for the full output from running initdb-oracle.sql using sqlplus. The really suspicious bit is: SP2-0734: unknown command beginning "constraint..." - rest of line ignored. SP2-0042: unknown command ")" - rest of line ignored. create index lxr_i_indexes on lxr_indexes(symid) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2773972&group_id=27350 |
|
From: Malcolm B. <mal...@gm...> - 2009-04-17 10:55:41
|
I'll have a look and check today. M On Sat, Apr 11, 2009 at 11:31 AM, Adrian Issott <adr...@ho...> wrote: > Hi Malcolm, > > Would you mind check that the patch attached to this bug report works on > linux? > > Cheers, > Adrian > >> To: no...@so... >> From: no...@so... >> Date: Sat, 11 Apr 2009 10:28:41 +0000 >> Subject: [Lxr-dev] [ lxr-Bugs-2752574 ] The LXR general text search >> doesn't work with Swish on Windo >> >> Bugs item #2752574, was opened at 2009-04-11 11:24 >> Message generated for change (Comment added) made by adrianissott >> You can respond by visiting: >> >> https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2752574&group_id=27350 >> >> Please note that this message will contain a full copy of the comment >> thread, >> including the initial issue submission, for this request, >> not just the latest update. >> >Category: Browsing >> >Group: v0.9.6 >> Status: Open >> Resolution: None >> >Priority: 6 >> Private: No >> Submitted By: AdrianIssott (adrianissott) >> >Assigned to: AdrianIssott (adrianissott) >> Summary: The LXR general text search doesn't work with Swish on Windo >> >> Initial Comment: >> Performing a general text search for any thing at all when using Swish and >> a webserver on Windows results in output such as the attached >> "broken_search.html". >> >> ---------------------------------------------------------------------- >> >> >Comment By: AdrianIssott (adrianissott) >> Date: 2009-04-11 11:28 >> >> Message: >> What seems to be happening is that the output of swish is being shown >> directly in the HTML and not being formatted by the search script. I've >> attached a patch that avoids complicated use of pipes that works on >> windows. >> >> ---------------------------------------------------------------------- >> >> You can respond by visiting: >> >> https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2752574&group_id=27350 >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> High Quality Requirements in a Collaborative Environment. >> Download a free trial of Rational Requirements Composer Now! >> http://p.sf.net/sfu/www-ibm-com >> _______________________________________________ >> Lxr-developer mailing list >> Lxr...@li... >> https://lists.sourceforge.net/lists/listinfo/lxr-developer > > ________________________________ > Surfing the web just got more rewarding. Download the New Internet Explorer > 8 |
|
From: SourceForge.net <no...@so...> - 2009-04-17 10:53:11
|
Feature Requests item #742274, was opened at 2003-05-23 12:54 Message generated for change (Comment added) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=742274&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Interface Group: None >Status: Closed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: More info from dentifier search display. Initial Comment: The identifier search such as: http://sourcenav/lxr/ident?v=<version>?i=<ident> does not return enough information compared with the freetext search. It would be perfect if each indentifier in the list displayed the content of the line as well, just like the freetext search. Thanks ---------------------------------------------------------------------- >Comment By: Malcolm Box (mbox) Date: 2009-04-17 11:53 Message: Duplicate of 741648 ---------------------------------------------------------------------- Comment By: AdrianIssott (adrianissott) Date: 2009-04-12 11:08 Message: This is a duplicate of Feature Request 741648 (More info from dentifier search display) and should be closed. See https://sourceforge.net/tracker/?func=detail&aid=741648&group_id=27350&atid=390120. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=742274&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-17 10:43:35
|
Bugs item #2758373, was opened at 2009-04-13 10:37 Message generated for change (Settings changed) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2758373&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: v0.9.6 >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: AdrianIssott (adrianissott) Assigned to: AdrianIssott (adrianissott) Summary: Invalid Perl Identifier References Initial Comment: The attached zip file contains the result of doing an identifier search for char_2_int which gives references on lines 31, 32 and 52. However, the html.pl source file (also in the zip) shows char_2_int occurring on lines 44 and 72. This occurs when using plain files with either MySql or PostGreSql as the database. ---------------------------------------------------------------------- Comment By: AdrianIssott (adrianissott) Date: 2009-04-13 11:07 Message: The issue occurred as a result of the following line in generic.conf for the perl langmap: 'atom' => ('\$\W?', ''), The atom keyword in the language spec is normally used to ignore characters such as \", \' and \# to prevent them from otherwise incorrectly terminating other language specs such as strings and comments. However, the above atom pattern matches perfectly normal things such as $! and $? which don't seem to affect the other spec patterns. Certainly the perl parsing is now much improved as a result of removing this line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2758373&group_id=27350 |
|
From: Malcolm B. <mal...@gm...> - 2009-04-17 10:29:27
|
Hi Adrian, I've been moving directories/files for testing to the lxr-tools module in the test-data directory - it looks like this commit is adding some test files into the main lxr module. The main reason for this is to separate out the development infrastructure from the released code - although I haven't moved the actual test code yet (perhaps this would be worth doing). How do you feel about moving this across to the lxr-tools module? Cheers, Malcolm On Fri, Apr 10, 2009 at 9:29 PM, AdrianIssott <adr...@us...> wrote: > Update of /cvsroot/lxr/lxr/tests/test-src > In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv10674/tests/test-src > > Log Message: > Directory /cvsroot/lxr/lxr/tests/test-src added to the repository > > > > ------------------------------------------------------------------------------ > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > _______________________________________________ > Lxr-commits mailing list > Lxr...@li... > https://lists.sourceforge.net/lists/listinfo/lxr-commits > |
|
From: SourceForge.net <no...@so...> - 2009-04-17 10:22:57
|
Feature Requests item #1691378, was opened at 2007-03-30 16:37 Message generated for change (Settings changed) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=1691378&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None Status: Open Priority: 5 Private: No Submitted By: Paul D. Smith (psmith) >Assigned to: AdrianIssott (adrianissott) Summary: Rearchitect the DB backends Initial Comment: The LXR index DB backends all use DBI, which is perfect, but they don't take enough advantage of it and thus end up duplicating a significant amount of code with all the problems that generally brings. Perl's DBI is ALREADY a generic front-end for SQL databases of all different types, so having separate LXR::Index::* subclasses for each database is largely unnecessary: all databases can use the DBI interface almost exactly the same way. There are minor differences, though, so it's not true that we can get rid of the LXR::Index::* database specific classes entirely. I propose that we make LXR::Index a proper superclass for the DB-specific subclasses, and we push up as much functionality as possible into the superclass. The subclasses should be pretty small: they will deal only with DB-specific issues (for example, auto-incremented fields which work differently in PostgreSQL and MySQL). ---------------------------------------------------------------------- Comment By: AdrianIssott (adrianissott) Date: 2009-04-13 17:39 Message: I'd like to take this on as I'd also noticed a lot of redundancy in the LXR::Index modules. Malcolm can you assign it to me? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=1691378&group_id=27350 |
|
From: SourceForge.net <no...@so...> - 2009-04-13 16:39:19
|
Feature Requests item #1691378, was opened at 2007-03-30 16:37 Message generated for change (Comment added) made by adrianissott You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=1691378&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: None Status: Open Priority: 5 Private: No Submitted By: Paul D. Smith (psmith) Assigned to: Nobody/Anonymous (nobody) Summary: Rearchitect the DB backends Initial Comment: The LXR index DB backends all use DBI, which is perfect, but they don't take enough advantage of it and thus end up duplicating a significant amount of code with all the problems that generally brings. Perl's DBI is ALREADY a generic front-end for SQL databases of all different types, so having separate LXR::Index::* subclasses for each database is largely unnecessary: all databases can use the DBI interface almost exactly the same way. There are minor differences, though, so it's not true that we can get rid of the LXR::Index::* database specific classes entirely. I propose that we make LXR::Index a proper superclass for the DB-specific subclasses, and we push up as much functionality as possible into the superclass. The subclasses should be pretty small: they will deal only with DB-specific issues (for example, auto-incremented fields which work differently in PostgreSQL and MySQL). ---------------------------------------------------------------------- Comment By: AdrianIssott (adrianissott) Date: 2009-04-13 17:39 Message: I'd like to take this on as I'd also noticed a lot of redundancy in the LXR::Index modules. Malcolm can you assign it to me? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390120&aid=1691378&group_id=27350 |
6 messages has been excluded from this view by a project administrator.
