From: Allison N. <dem...@ma...> - 2010-03-20 23:02:57
|
I'm not an expert, but super will call the superclass in ruby. It might be a bridge proxy object, not the cocoa "superclass". Sorry I'm not in front of a computer, so I can't check the source, but I'm guessig that's why super_xxxx is used Hope that helps. Envoyé de mon iPhone Le 20 mars 2010 à 21:55, Eric Christopherson <ech...@gm...> a écrit : > On Fri, Mar 19, 2010 at 5:15 AM, Allison Newman <dem...@ma...> > wrote: >> Yup, its a bridge thing. You'll notice that the init method that I >> defined >> in the last post does the same thing as the hillegass example. As >> long as >> you stay on one side of the bridge or the other, you can do as you >> please, >> but as soon as you cross the bridge using super_ you have to keep >> the same >> signature. > > Is the bridge also the reason you can't just use super(...)? > > --- > --- > --- > --------------------------------------------------------------------- > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Rubycocoa-talk mailing list > Rub...@li... > https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk |