Gather autocompletion-information while running tests?

Discussion in 'Ruby' started by Jan Kechel, Aug 14, 2010.

  1. Jan Kechel

    Jan Kechel Guest

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: RIPEMD160


    Hi everybody,

    I was looking around for some autocompletion solution for ruby. Most
    sites tell me that ruby is too dynamic to write any simple IDE
    supporting this.

    I came accross the following idea:

    Let's collect the information we need for autocompletion during running
    tests.

    Basically we need to know, what variable names in which functions (and
    in which files) are instantiated as what kind of objects.
    Then we could lookup all the available methods of those objects (either
    a static list, or also looked up during the tests running).

    Wouldn't that be a very easy solution for autocompletion? (though not
    100% complete as it won't work for newly named variables)

    The good side-effect would be that from then everyone would have even
    more reasons to write good test coverage ;)

    I played around a little with set_trace_func, but i'm missing the local
    variablenames here.

    Probably the best would be to write a Ruby C extension that creates
    something like (or exactly) ctags file to be interpreted by vim.

    What are your thoughts?

    Jan Kechel

    - --
    publictimestamp.org/ptb/PTB-9682 sha224 2010-08-14 12:15:42
    267159826FCA305616B0A8A4DC01999AC0E80150A72CC14E4B668B7C

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.10 (GNU/Linux)

    iQIcBAEBAwAGBQJMZpKEAAoJEI0XMg7eH/Qc6lsP/2usLaEpeiqICD32Ic5g8t2p
    y9i9vwQf7B/Uw1sGcdqYQ5JNV20Dmz2+lDiRCifKO6ndzJcXp3VbJix7+z8/L+fQ
    KdY7E+WpHnFqSa0cQl4b4cVjhIjSUrYv4UselQSkeXKOVO9DQJFXph9S/TZ5/Clx
    0UnMZF4wAnUhkz3k9/HjWA6fx8W6Z2HneLqaOVN8SLU9H+90gdDFfdHOvI30veUt
    5opV6ukJBrqnJrYkvwW1jHuMTHYAjNLCASMg6nYo8eLz/eNPPZmdtBQEtx8dV9Iw
    QqGBt+iTYkin7K3ZPb4h/3iJthYlzd78B9RxLEhxL3pvrWLWL4yxE3sp7Iq+TKeG
    mLdLqMwYNO0Lhcx7fyAD0yuMc7Nm5N4Nv24HV9mUihtrjNUdAKf1Fbjwcu9lUs4Z
    BsO+bll7Svgy6r0s8pXwpOA+6PPgYIRyJaLaMBMr9fQn0lVBK4RsjtF+l6rINiXy
    xeJO3C8U8QXmox/tEUuadR+O3CFeFqvvJ5HQ5vt0uUFOVSS0oAgQgF9S7Afq8EpX
    rjKiw/Dr/avCMGgi3+B/BUmnjFfUB//hXV+oMK/jx+CYamT7lXvMfbemNznIcBr6
    Z8aZs/1hRJzy4XH9SzkTR8ip6dG5+djTNYW/+FDdtG3xJrbQ9YxjoWArRP4FYQr6
    GxZgyCr/FTqkIFkpKHP4
    =t9Jd
    -----END PGP SIGNATURE-----
    Jan Kechel, Aug 14, 2010
    #1
    1. Advertising

  2. Jan Kechel

    Roger Pack Guest


    > Basically we need to know, what variable names in which functions (and
    > in which files) are instantiated as what kind of objects.
    > Then we could lookup all the available methods of those objects (either
    > a static list, or also looked up during the tests running).
    >
    > Wouldn't that be a very easy solution for autocompletion? (though not
    > 100% complete as it won't work for newly named variables)


    Is static analysis not enough for you?
    --
    Posted via http://www.ruby-forum.com/.
    Roger Pack, Aug 17, 2010
    #2
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. ABC
    Replies:
    1
    Views:
    428
    DavidG
    Jan 13, 2006
  2. Klaus Neuner
    Replies:
    14
    Views:
    450
    Paul McGuire
    Dec 15, 2004
  3. cyprian

    an autocompletion algorithm

    cyprian, May 22, 2007, in forum: Java
    Replies:
    0
    Views:
    350
    cyprian
    May 22, 2007
  4. Papalagi Pakeha
    Replies:
    2
    Views:
    246
    Papalagi Pakeha
    Jun 12, 2007
  5. Florencio Cano
    Replies:
    1
    Views:
    317
Loading...

Share This Page