Rob . wrote:
Yes, the completion list shows parameter names - it's inserting them
too at the moment.
Very nice, can't wait to test this. 
Regards,
Peter
Yeah, I realise that. Thanks!
···
On Wed, 30 Mar 2005 22:53:22 +0900, James Edward Gray II <james@grayproductions.net> wrote:
But you need to execute the entire program right down to the line where
completion is requested for that eval() return anything useful. A
program could have many "a" variables. Executing the code is an
unrealistic requirement; way too many possible external dependancies.
From Chad's description, I believe that is correct.
... unit tests work great for this ...
···
On 29 Mar 2005, at 23:04, Nospam wrote:
Eric Hodel wrote:
http://www.chadfowler.com/index.cgi/Computing/Programming/Ruby/ TypeWatching.rdoc,v
It would be nice to see this somehow integrated in IDE's, but this still means the code needs to be executed somehow before the typehints are available, not?
--
Eric Hodel - drbrain@segment7.net - http://segment7.net
FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04
From the readme of irb enhancements (http://www.creo.hu/~csaba/ruby/\):
irb-completion-enhanced.rb
Context-sensitive completion for irb.
[snip]
There is one more feature: an attribute named watch_ancestors of
IRB::InputCompletor. If is it set to true, method name completion will
behave in the familiar way. If set to false, only the own methods of the
object (and its class) are shown. And if it's nil, then each hit on the
tab key switches between these two behaviours (this latter is the
default). This is useful eg. when you want to explore a new ruby class
(I guess at such an occasion your focus is not on being notified to the
fact that the object responds to is_complex_yaml? ...)
Csaba
···
On 2005-03-30, Eric Hodel <drbrain@segment7.net> wrote:
Have you used Readline tab completion in irb? It is far from useful,
giving you too many potential completions from too far up the
inheritance tree.
Hello Eric,
···
On 29 Mar 2005, at 23:04, Nospam wrote:
Eric Hodel wrote:
http://www.chadfowler.com/index.cgi/Computing/Programming/Ruby/
TypeWatching.rdoc,vIt would be nice to see this somehow integrated in IDE's, but this
still means the code needs to be executed somehow before the typehints
are available, not?
From Chad's description, I believe that is correct.
... unit tests work great for this ...
But unit tests sometimes use other objects (Mock classes) then the
"normal" classes. So the results can be misinterpreted.
But even with unit tests the application under development will
normally run a thousand times during a development week.
--
Best regards, emailto: scholz at scriptolutions dot com
Lothar Scholz http://www.ruby-ide.com
CTO Scriptolutions Ruby, PHP, Python IDE 's