blocks|key|348318|text|我认为公共方法是对象的某种接口，将它们放在最突出的位置，即文件的顶部，这是合乎逻辑的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348319|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think that public methods is a some kind of interface of the object, and it's logical to place them on the most prominent place i.e. in the top of file.

blocks|key|348351|text|您不需要将public或private放在每个方法之上。我通常把我所有的私有方法放在类的底部。此外，也不必显式地声明public，因为默认情况下方法是公共的。例如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|348352|class+FooBar

++def+some_public_method
++end

++def+another_public_method
++end

private

++def+some_private_method
++end

++def+another_private+method
++end

end|code-block|syntax|javascript|348353|entityMap^0|5|6|C|7|1M|6|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|L|$]]

You don't need to put <code>public</code> or <code>private</code> above each method. I usually put all of my private methods at the bottom of my class. Also, don't have to explicitly say <code>public</code> as methods are public by default. For example:

<pre><code>class FooBar

 def some_public_method
 end

 def another_public_method
 end

private

 def some_private_method
 end

 def another_private method
 end

end
</code></pre>

blocks|key|348402|text|正如其他人已经指出的那样，约定是将私有方法放在底部，放在一个私有类下。然而，您可能还应该知道，许多程序员为此使用双缩进(4个空格而不是2个)方法。原因是，通常情况下，您不会在文本编辑器中看到“私有”，并认为它们可能是公共的。如下图所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348403|class+FooBar

++def+some_public_method
++end

++def+another_public_method
++end

private

++++def+some_private_method
++++end

++++def+another_private+method
++++end

end|code-block|syntax|javascript|348404|此方法应避免您必须上下滚动，并将使其他程序员在您的代码中更舒适。|348405|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

As others have already pointed out the convention is to put private methods at the bottom, under one private class. However, you should probably also know that many programers use a double indented (4 spaces instead of 2) method for this. The reason is that often times you won't see "private" in your text editor and assume they could be public. See below for an illustration:

<pre><code>class FooBar

 def some_public_method
 end

 def another_public_method
 end

private

 def some_private_method
 end

 def another_private method
 end

end
</code></pre>

This method should prevent you from having to scroll up and down and will make other programmers more comfortable in your code.

blocks|key|348481|text|我不喜欢为每个方法指定public或private。将所有的私有方法放在底部，让我在每个文件中都有一个“私有”的实例。我想这是品味的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348482|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I don't like having to specify public or private for each method. Putting all private methods at the bottom lets me have a single instance of "private" per file. I guess it's a matter of taste.

blocks|key|348544|text|在我看来，最好的做法是按顺序声明你的方法，而不是保持私密的观点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|348545|最后，只需添加：private+:xmethod，就可以使任何方法成为私有方法|offset|length|style|CODE|348546|示例：|348547|class+Example
+def+xmethod
+end

+def+ymethod
+end

+def+zmethod+
+end

+private+:xmethod,+:zmethod

end|code-block|syntax|javascript|348548|这能证明你的问题是正确的吗？|348549|entityMap^0|0|8|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|X|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

The best practice in my point of view is to go sequentially and declare your methods without keeping private in point of view.

At the end, you can make make any method private by just adding: <code>private :xmethod</code>

Example:

<pre><code>class Example
 def xmethod
 end

 def ymethod
 end

 def zmethod 
 end

 private :xmethod, :zmethod

end
</code></pre>

Does this justify your question?

blocks|key|348601|text|我来自java背景，我讨厌必须滚动才能看到方法类型。我认为一个人不能在没有丑陋的情况下指定每个方法的方法可见性，这是疯狂的。因此，我最终在每个suck方法之前放置了一个注释#private，然后声明private+:...。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|348602|更新:在最近的ruby中，人们可以编写private+def+method_name，所以上面的内容就不那么重要了。|348603|更新2:实际查看@devpuppy的答案，它有更多的解释。|348604|entityMap^0|2E|8|2R|C|0|J|N|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

I'm coming from java background and I hate to have to scroll to see method type. I think it's insane that one cannot specify method visibility per method without ugliness. So I ended up putting a comment <code>#private</code> before each suck method and then declaring <code>private :...</code>.
Update: In recent ruby one can write <code>private def method_name</code> so the above is much less relevant.
Update 2: actually see @devpuppy's answer, it has more explanation.

blocks|key|348642|text|从Ruby2.1开始，还可以选择将private添加到方法定义中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|348643|class+Example
+def+xmethod
+end

+private+def+ymethod
+end

+private_class_method+def+self.zmethod+
+end
end|code-block|syntax|javascript|348644|您可以立即看到一个方法是否是私有的，无论它在(大)文件中的什么位置。它与许多其他语言都是一致的。但它的打字量更大，不能很好地对齐。|348645|entityMap^0|H|7|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

There's also the option to prepend <code>private</code> to the method definition since Ruby 2.1.
<pre><code>class Example
 def xmethod
 end

 private def ymethod
 end

 private_class_method def self.zmethod 
 end
end
</code></pre>
You can instantly see if a method is private, no matter where in the (large) file it is. And it's consistent with many other languages. But it's a bit more typing and doesn't nicely align.

blocks|key|564791|text|Dennis有一个完美的答案，那就是，当使用ruby+>=2.1时，只需在def前面加上私有(或受保护的公共)即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|564792|但我认为现在也可以使用private作为块，如下所示：|564793|private+begin
+++def+foo
+++end
+++def+bar
+++end
end

def+zip
end|code-block|syntax|javascript|564794|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Dennis had the perfect answer, that is, when using ruby >=2.1, just prefix the def with private (or protected,public)

But I believe that it's now also possible to use private as a block
as in:

<pre><code>private begin
 def foo
 end
 def bar
 end
end

def zip
end
</code></pre>

blocks|key|348806|text|一种方式是将方法分组在一起，这样每个类最多只使用一次private和protected。另一种方式是在方法定义之后指定可见性：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|348807|class+Example
++def+my_private_method
++end
++private+:my_private_method

++def+my_public_method
++end
end|code-block|syntax|javascript|348808|从Ruby2.1.0开始，def以符号的形式返回方法名，因此可以使用更流线型的样式：|348809|class+Example
++private+def+my_private_method
++end

++def+my_public_method
++end

++protected+def+my_protected_method
++end

++private_class_method+def+self.my_private_class_method
++end
end|348810|(请注意，我们对类方法使用private_class_method+--否则我们将得到NameError:+undefined+method，因为private需要一个实例方法。即使像在原始示例中那样将其用作宏，它也只影响实例方法的可见性。)|348811|我最喜欢这种内联可见性风格，因为它允许你随心所欲地组织方法。它降低了在错误的位置添加新方法并无意中将其设置为私有的风险。|348812|至于类方法语法，您可以这样处理：|348813|class+Example
++private+def+my_private_method
++end

++class+<<+self
++++private+def+my_private_class_method
++++end
++end
end|348814|entityMap^0|Q|7|Y|9|0|0|D|3|0|0|D|K|17|R|21|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|17|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1F|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1G|8|@]|D|@]|E|$]]|$1|U|3|V|5|H|7|1H|8|@]|D|@]|E|$I|J]]|$1|W|3|-4|5|6|7|1I|8|@]|D|@]|E|$]]]|X|$]]

One style is to group methods together so that you only use <code>private</code> and <code>protected</code> once per class at most. Another style is to specify visibility right after the method definition:

<pre><code>class Example
 def my_private_method
 end
 private :my_private_method

 def my_public_method
 end
end
</code></pre>

As of Ruby 2.1.0 <code>def</code> returns the method name as a symbol, so a more streamlined style is possible:

<pre><code>class Example
 private def my_private_method
 end

 def my_public_method
 end

 protected def my_protected_method
 end

 private_class_method def self.my_private_class_method
 end
end
</code></pre>

(Note that we use <code>private_class_method</code> for class methods -- otherwise we'd get <code>NameError: undefined method</code> since <code>private</code> expects an instance method. Even when using it as a macro like in the original example it only affects the visibility of instance methods.)

I like this inline visibility style best, as it allows you to organize methods as you wish. It decreases the risk of adding a new method in the wrong place and inadvertently making it private.

As for the class method syntax, you can handle it this way instead:

<pre><code>class Example
 private def my_private_method
 end

 class &lt;&lt; self
 private def my_private_class_method
 end
 end
end
</code></pre>

Most of the blogs or tutorials or books have private methods at the bottom of any class/module. Is this the best practice?

I find having private methods as and when necessary more convenient. For example:

<pre><code>public
def my_method
 # do something
 minion_method
end

private
def minion_method
 # do something
end

public
def next_method
end
</code></pre>

This way I find the code more readable instead of scrolling up and down continuously which is very irritating.

Is there something terribly wrong in this approach? Is having private methods at the bottom not just a best practice and something else?

Where to place private methods in Ruby?

大多数博客、教程或书籍在任何类/模块的底部都有私有方法。这是最佳实践吗？我发现在必要的时候使用私有方法更方便。例如：publicdef my_method  # do something  minion_methodendprivatedef minion_method  # do somethingendpublic...

问Ruby中的私有方法放在哪里？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ruby中的私有方法放在哪里？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ruby中的私有方法放在哪里？
EN