Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#22 Deprecate or Remove Unused LXR::Lang Modules

closed
AdrianIssott
General (16)
5
2009-04-22
2009-04-19
AdrianIssott
No

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.

Discussion

  • Malcolm Box
    Malcolm Box
    2009-04-20

    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.

     
  • Malcolm Box
    Malcolm Box
    2009-04-20

    • assigned_to: nobody --> adrianissott
     
  • 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 ...

     
  • 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.

     
  • Malcolm Box
    Malcolm Box
    2009-04-21

    I say nuke the Lang modules.

    Don't know whether the DB module works or not - I'll give it a test to see.

     
  • Malcolm Box
    Malcolm Box
    2009-04-22

    Modules zapped!

     
  • Malcolm Box
    Malcolm Box
    2009-04-22

    • status: open --> closed