Ruby/Tk article on macdevcenter

[Phil Tomson]

Hadn't seen this mentioned yet:

http://www.macdevcenter.com/pub/a/mac/2004/06/25/ruby_pt1.html


Phil

 

[Tim Hunter]

Hadn't seen this mentioned yet:

http://www.macdevcenter.com/pub/a/mac/2004/06/25/ruby_pt1.html


Phil

Timely. I'm just about to embark on my first Ruby/Tk application.

That "default initialize" method, though, the one with no arguments. That's
just not right. I believe the 2nd definition of initialize is going to
override the "default" one. Let's see:

[tim: ~]$ ruby -w rb/CronJobMgr.rb
rb/CronJobMgr.rb:95: warning: method redefined; discarding old initialize

Yup.

 

[Martin DeMello]

Hadn't seen this mentioned yet:

http://www.macdevcenter.com/pub/a/mac/2004/06/25/ruby_pt1.html

Sadly the guy seems rather new to Ruby - his overloaded initialize method
is a glaring C++ism. I've written to him about it; hopefully the code
can be changed.

martin

 

[gabriele renzi]

il 19 Jul 2004 21:37:37 GMT, (e-mail address removed) (Phil Tomson) ha
scritto::

Hadn't seen this mentioned yet:

http://www.macdevcenter.com/pub/a/mac/2004/06/25/ruby_pt1.html

this made me notice this:
ruby -e "self.puts 'ciao' "
-e:1: private method `puts' called for main:Object (NoMethodError)

why this error appears?

 

[Stephan Kämper]

il 19 Jul 2004 21:37:37 GMT, (e-mail address removed) (Phil Tomson) ha
scritto::




this made me notice this:
ruby -e "self.puts 'ciao' "
-e:1: private method `puts' called for main:Object (NoMethodError)

why this error appears?

puts is - as the error message says, a privat method.
In Ruby - if memory serves right - private methods can only be called
with an implicit receiver.

A citation from the pickaxe: "Private methods cannot be called with an
explicit receiver. Because you cannot specify an object when using them,
private methods can be called only in the defining class and by direct
descendents within that same object."

Stephan

 

[ts]

"S" == =?ISO-8859-1?Q?Stephan K=E4mper?= <ISO-8859-1> writes:

S> puts is - as the error message says, a privat method.
S> In Ruby - if memory serves right - private methods can only be called
S> with an implicit receiver.

svg% ruby -e 'Kernel.puts "I am a Kernel module function"'
I am a Kernel module function
svg%



Guy Decoux

 

[gabriele renzi]

S> puts is - as the error message says, a privat method.
S> In Ruby - if memory serves right - private methods can only be called
S> with an implicit receiver.

svg% ruby -e 'Kernel.puts "I am a Kernel module function"'
I am a Kernel module function

well, but since=> true
then why self.puts fails?
Is the explanation
"you can't call methods in included modules with self.method" ?

 

[ts]

g> "you can't call methods in included modules with self.method" ?

yes and no

a module function is a private method and a public class method.

When you include a module, you have access only to the methods (not the
class methods). If an object, except Kernel, try to access puts it
will have the private method



Guy Decoux