C# Accessors "Get" return

Question

1.00/5 (1 vote)

See more:

Hi, How come C# requires a "return" statement within a get{} ??
Isn't it obvious that you would want to return something?

thanks

Posted 14-Feb-15 12:29pm

shiftwik

Add a Solution

Comments

Valery Possoz 14-Feb-15 18:50pm

Sometimes the get is pretty complex and you need to specify what is returned. How would you do it otherwise?
If you want something simpler just use a variable.

PIEBALDconsult 14-Feb-15 19:08pm

And you may want more than one.

Sergey Alexandrovich Kryukov 14-Feb-15 20:35pm

How about thinking a bit before asking? All you had to do was to think a bit. And you could explain your idea showing some alternative syntax, if you thought it was possible.
—SA

phil.o 15-Feb-15 2:06am

Nothing is "obvious" for a computer. If a code must return something, it must do it with the return statement, there is no other way.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2015-02-14T14:33:00

This question is exactly the same as asking: "how come 'return' statement is required for all non-void functions? Isn't it obvious that you would want to return something?"

In other word, this question lacks elementary logic. Yes, a need for return is obvious from the signature of a function or a property (again, there is no difference in this respect). But this is not enough. What value should be returned and at what point? This is expressed by the return statement.

Also, this question means seeing no difference between declaration and definition, and also between declaration and statement. The language (as well as the languages where C# return was derived from) is not a declarative language. Statements actually code some action, something really happening to the computer registers, memory or ports. If you declare some function with, say, arguments and return type, eventually the definition needs to specify some action using these parameters and assignment return value or object to something.

—SA