Re: How to approach indexing source code?

2014-06-05 Thread Johan Tibell
x source file or > compiler output. Try doing some proof of concept. You will get some idea of > how to move forward. > > Regards > Aditya > www.findbestopensource.com > > > > > On Thu, Jun 5, 2014 at 2:48 PM, Johan Tibell > wrote: > > > By "index the

Re: How to approach indexing source code?

2014-06-05 Thread Johan Tibell
t; Just keep it simple. Index the entire source file. One source file is one > document. While indexing preserve dot (.), Hypen(-) and other special > characters. You could use whitespace analyzer. > > I hope it helps > > Regards > Aditya > www.findbestopensource.com &g

Re: How to approach indexing source code?

2014-06-04 Thread Johan Tibell
> > > Regards > Aditya > www.findbestopensource.com > > > > > On Wed, Jun 4, 2014 at 7:02 AM, Johan Tibell > wrote: > > > Hi, > > > > I'd like to index (Haskell) source code. I've run the source code > through a > > compiler

How to approach indexing source code?

2014-06-03 Thread Johan Tibell
Hi, I'd like to index (Haskell) source code. I've run the source code through a compiler (GHC) to get rich information about each token (its type, fully qualified name, etc) that I want to index (and later use when ranking). I'm wondering how to approach indexing source code. I can see two possib