Skip to content

Update README.md #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 8, 2021
Merged

Update README.md #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions exercises/05-Defining-vs-Calling-a-function/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ tutorial: "https://www.youtube.com/watch?v=fz4ttmwZWuc"

# `05` Defining vs Calling a function

Functions will only exists if you or somebody else defines them... is the only way the language compiler/interpreter knows they exist, therefore is able to run them when you call them.
Functions will only exists if you or somebody else defines them... it is the only way the language compiler/interpreter knows they exist, therefore it's able to run them when you call them.

To define a function we need to write this basic code formula:

Expand Down Expand Up @@ -34,7 +34,7 @@ this is called **the scope**, and it could be local (inside the function)
and global (outside of the function).

**The Return**: not every function needs to return something, but it is recommended that it does.
Tip: returning `None` is a good default for when you, still, doesn't know if you need to return something.
Tip: returning `None` is a good default for when you, still, don't know if you need to return something.

Example of a function:

Expand Down