Slashdot Mirror

← Back to Stories (view on slashdot.org)

Search Engine For Coders to Launch

Posted by Zonk on from the sounds-codetacular dept.

karvind writes "According to Wired, 'Krugle' is set to next month. The search engine indexes programming code and documentation from open-source repositories like SourceForge, and includes corporate sites for programmers like the Sun Developer Network. The index will contain between 3 and 5 terabytes of code by the time the engine launches in March. According to article, Krugle also contains intelligence to help it parse code and to differentiate programming languages, so a PHP developer could search for a website-registration system written in PHP simply by typing 'PHP registration system.'" Update: 02/17 21:04 GMT by Z : Summary edited for accuracy.

4 of 149 comments (clear)

  1. Where does it say that Google is launching it? by frangipani · · Score: 3, Interesting

    This sounds like a new company, not a product of Google.

  2. Community? by binaryDigit · · Score: 4, Interesting

    Some other interesting features above and beyond simple searching could be:

    - merge with semantic web work to be able to search on higher level concepts (e.g. if I type "bubble sort" it returns all bubble sorting code even if it doesn't explicitly say "bubble sort" anywhere).

    - "community" features that allow developers to leave comments on code (no, not comments _in_ code, but on code, similar to epinions et al).

    - if this index is available via api like the main google index, then people could do things like have automated lint type tools.

    - code chain. If I search for some code, then it'd be nice to be able to then peruse that codes hierarchy within the search engine (vs having to download it or cvs over to it).

  3. So how long.... by Jaysyn · · Score: 2, Interesting

    ...till Microsoft, SAP, SCO (remember them?) etc start polluting this repository with proprietary code?

    Jaysyn

    --
    There is a war going on for your mind.
  4. Oops, small code bug by Medievalist · · Score: 2, Interesting

    OK, that code exits dirty at EOF. Needs a small modification to pass exit status of read back through function return to main while loop:

    ReadFields () {
            local IFS=:
            Host="#"
            while [ `expr substr $Host 1 1` = "#" ]
                do
                        read Host Key Interval Excludes Keep || return
            done
    }

    Still ugly and inelegant, in my opinion, but at least it seems to work... and it has an explicit EOF return now, which is probably a good thing.