blocks|key|219757|text|这可能没有区别。IIRC，编译器生成的IL将它们都转换为返回语句，除非有额外的_returnValue变量的用法。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|219758|在我看来，FunctionName赋值的可读性很差，这是一个坏的VB6习惯的例子。我也更喜欢_returnValue+(不是RETVAL)变量方法。|219759|entityMap^0|W|L|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

There is probably no difference. IIRC, the compiler generated IL converts them both into Return statements unless there is additional usage of a _returnValue variable. 

The readability of the FunctionName assignment is poor in my opinion, and an example of a bad VB6 habit. I prefer the _returnValue (NOT RETVAL) variable method also.

blocks|key|4284936|text|不同的是他们做了不同的事情！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4284937|“'Return”做了两件事：|4284938|4284939|它设置该点的函数返回值2.它会立即退出|ordered-list-item|4284940|函数|4284941|函数中的任何代码都不会执行！|4284942|‘'Functionname+=+value’做一件事:+1.它在那个点设置函数的返回值|4284943|函数中的其他代码将继续执行，这使其他逻辑能够优化或覆盖函数返回值|4284944|差别很大，伙计们。记住，这并不全是关于状态的，它也是关于流程的。|4284945|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

The difference is that they DO DIFFERENT THINGS! 

'Return value' does 2 things: 
1. It sets the function return value at that point
2. It immediately exits the function

No further code in the function executes!

'Functionname = value' does 1 thing:
1. It sets the function return value at that point

Other code in the function continues to execute
This enables additional logic to refine or override the function return value

Huge difference folks. Remember it's not all about state, it's also about flow.

blocks|key|219845|text|我们来看看..。奇怪的是，"functionName+=“产生的IL更少？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|219846|代码：|219847|Public+Function+Test()+As+String
++++Test+=+"Test"
End+Function


Public+Function+Test2()+As+String
++++Return+"Test"
End+Function|code-block|syntax|javascript|219848|IL：|219849|.method+public+static+string+Test()+cil+managed
{
++++.maxstack+1
++++.locals+init+(
++++++++[0]+string+Test)
++++L_0000:+nop+
++++L_0001:+ldstr+"Test"
++++L_0006:+stloc.0+
++++L_0007:+ldloc.0+
++++L_0008:+ret+
}

.method+public+static+string+Test2()+cil+managed
{
++++.maxstack+1
++++.locals+init+(
++++++++[0]+string+Test2)
++++L_0000:+nop+
++++L_0001:+ldstr+"Test"
++++L_0006:+stloc.0+
++++L_0007:+br.s+L_0009
++++L_0009:+ldloc.0+
++++L_000a:+ret+
}|219850|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Let's take a look... Oddly the "functionName =" generates less IL? 

Code:

<pre><code>Public Function Test() As String
 Test = "Test"
End Function


Public Function Test2() As String
 Return "Test"
End Function
</code></pre>

IL:

<pre><code>.method public static string Test() cil managed
{
 .maxstack 1
 .locals init (
 [0] string Test)
 L_0000: nop 
 L_0001: ldstr "Test"
 L_0006: stloc.0 
 L_0007: ldloc.0 
 L_0008: ret 
}

.method public static string Test2() cil managed
{
 .maxstack 1
 .locals init (
 [0] string Test2)
 L_0000: nop 
 L_0001: ldstr "Test"
 L_0006: stloc.0 
 L_0007: br.s L_0009
 L_0009: ldloc.0 
 L_000a: ret 
}
</code></pre>

blocks|key|972537|text|执行以下操作仅供Visual+Basic+6.0开发人员轻松移植代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|972538|Public+Function+MyFunction()+As+String
++++MyFunction+=+"Hello"
End+Function|code-block|syntax|javascript|972539|如果您的项目包括没有使用过Visual+Basic+6.0的任何人，我绝对不建议继续使用它，因为这种语法会让人感到困惑。|972540|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Visual_Basic#Timeline^0|8|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

Doing the following is only provided for <a href="http://en.wikipedia.org/wiki/Visual_Basic#Timeline" rel="nofollow noreferrer">Visual Basic 6.0</a> developers to easily port code over:

<pre><code>Public Function MyFunction() As String
 MyFunction = "Hello"
End Function
</code></pre>

I would definitely not recommend keeping doing it if your project includes anyone who hasn't worked with Visual Basic 6.0, as this syntax will be confusing.

blocks|key|4284829|text|100次中有99次我会使用"return+value“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4284830|每隔一段时间，我就会有一个函数，其中的另一个类型不仅允许我保存变量声明，而且以一种实际上可以显著澄清该函数的方式来实现。通常，当我想要将返回值命名为与函数相同的名称时，通常会发生这种情况，而且这些返回值通常是递归函数；这种构造将其借给隐式返回变量。然而，这种情况非常少见。我不知道在我当前的项目中是否有使用隐式返回变量的函数。|4284831|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

99 times out of 100 I'll use "return value". 

Every once in a while I'll have a function where the other type not only allows me to save a variable declaration, but do it in a way that actually significantly clarifies the function. Usually this happens when I would want to name the return value the same as the function anyway, and often these are recursive functions; something about that construct lends it to the implicit return variable. However, that scenario is extremely rare. I don't know if I have any functions using implicit return variables at all in my current project.

blocks|key|977951|text|激活工具/选项/文本编辑器/所有语言/代码镜头时，引用计数将显示在每个Sub、Function或Property语句的上方。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|977952|"Return+Value“似乎比”为函数名赋值“更好。在后一种情况下，"Code+Lens“会产生一个夸大的引用计数。|977953|'+Code+Lens+reports+"0+references"+here+for+Sub+Rosa().
Public+Sub+Rosa()
++++Diagnostics.Debug.WriteLine(Test())
++++Diagnostics.Debug.WriteLine(Test2())
End+Sub

'+Code+Lens+reports+"2+references"+here+for+Function+Test().
Public+Function+Test()+As+String
++++Test+=+"Test"+++++++'+Code+Lens+counts+this+as+a+reference.
End+Function

'+Code+Lens+reports+"1+reference"+here+for+Function+Test2().
Public+Function+Test2()+As+String
++++Dim+strTest2+as+String+=+"Test"
++++Return+strTest2+++++'+Code+Lens+does+NOT+count+this+as+a+reference.
End+Function|code-block|syntax|javascript|977954|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|$]]

When Tools/Options/Text Editor/All Languages/Code Lens is activated, the Reference Count shows above each Sub, Function, or Property statement.

"Return Value" seems better than "assigning a value to the Functions Name". In the latter case, "Code Lens" produces an inflated Reference Count.

<pre><code>' Code Lens reports "0 references" here for Sub Rosa().
Public Sub Rosa()
 Diagnostics.Debug.WriteLine(Test())
 Diagnostics.Debug.WriteLine(Test2())
End Sub

' Code Lens reports "2 references" here for Function Test().
Public Function Test() As String
 Test = "Test" ' Code Lens counts this as a reference.
End Function

' Code Lens reports "1 reference" here for Function Test2().
Public Function Test2() As String
 Dim strTest2 as String = "Test"
 Return strTest2 ' Code Lens does NOT count this as a reference.
End Function
</code></pre>

blocks|key|3437492|text|在读到返回值语法是唯一一种真正的.NET方法之后，我想“好吧，我们就这样做吧”。然后我写了一个我知道的函数，从Return语句中返回一个值，或者在任何情况下返回一个异常，但仍然得到一个编译器警告，该函数“不会在所有路径上返回值”。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3437493|谢天谢地，我遇到了堆栈溢出问题，它解释了为什么；在我的例子中，向函数开头的过程名称添加一个默认值也可以避免出现警告。|3437494|因此，尽管出于语法一致性的考虑，我将继续使用返回值语法，但我也将为函数名分配一个默认值，以防止出现虚假警告而使编译过程变得混乱。|3437495|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/.NET_Framework^0|G|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

Having read that the Return Value syntax was the One True <a href="http://en.wikipedia.org/wiki/.NET_Framework" rel="nofollow noreferrer">.NET</a> Way Of Doing Things I thought "OK, we'll do it that way then". Then I wrote a function which I knew, hand on heart KNEW, returned either a value from a Return statement or alternatively an Exception under all circumstances, and still got a compiler warning that the function "doesn't return a value on all paths".

Thankfully I came across the Stack Overflow question <a href="https://stackoverflow.com/questions/3994368">How can I make this function not generate a “doesn't return a value on all paths” warning?</a> which explained why; adding a default value assignment to the procedure name at the head of the function prevented the warning in my case as well.

Consequently, even though I'll continue to use the Return Value syntax simply for the sake of syntax consistency, I'll also be assigning a default value to the function name just to prevent the possibility of cluttering up the compile process with bogus warnings.

blocks|key|3437560|text|在使用第三方工厂(_hsf)时非常方便，可以避免声明返回变量|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3437561|Public+Function+CreateExtremum(iShape+As+INFITF.Reference,+iDir1+As+HybridShapeTypeLib.HybridShapeDirection,+iSide1+As+Integer,+iDir2+As+HybridShapeTypeLib.HybridShapeDirection,+iSide2+As+Integer,+iDir3+As+HybridShapeTypeLib.HybridShapeDirection,+iSide3+As+Integer)+As+HybridShapeTypeLib.HybridShapeExtremum
++++CreateExtremum+=+_hsf.AddNewExtremum(iShape,+iDir1,+iSide1)
++++CreateExtremum.Direction2+=+iDir2
++++CreateExtremum.ExtremumType2+=+iSide2
++++CreateExtremum.Direction3+=+iDir3
++++CreateExtremum.ExtremumType3+=+iSide3
++++CreateExtremum.Compute()
End+Function|code-block|syntax|javascript|3437562|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

its quite handy when working with 3rd party factories(_hsf), you can avoid declaring return variables

<pre><code>Public Function CreateExtremum(iShape As INFITF.Reference, iDir1 As HybridShapeTypeLib.HybridShapeDirection, iSide1 As Integer, iDir2 As HybridShapeTypeLib.HybridShapeDirection, iSide2 As Integer, iDir3 As HybridShapeTypeLib.HybridShapeDirection, iSide3 As Integer) As HybridShapeTypeLib.HybridShapeExtremum
 CreateExtremum = _hsf.AddNewExtremum(iShape, iDir1, iSide1)
 CreateExtremum.Direction2 = iDir2
 CreateExtremum.ExtremumType2 = iSide2
 CreateExtremum.Direction3 = iDir3
 CreateExtremum.ExtremumType3 = iSide3
 CreateExtremum.Compute()
End Function
</code></pre>

In order to return a value from a VB.NET function one can assign a value to the "Functions Name" or use "return value."

I sometimes see these inter-mixed in the same function. Personally, I prefer the return.

My question is, what is the internal difference, if any, between the two?

VB.NET Function Return

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

为了从VB.NET函数返回值，可以给“函数名”赋值或使用“返回值”。我有时会在同一个函数中看到这些混合在一起。就我个人而言，我更喜欢回报。我的问题是，两者之间的内部差异是什么？

问VB.NET函数返回
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VB.NET函数返回EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VB.NET函数返回
EN