JavaScript: Expressions in definitions
We already know that expressions can be made up of several operations. But if you write an entire calculation in one long line, the code quickly becomes hard to read.
For example, this works:
const yuansCount = 50 * 1.25 * 6.91;
console.log(yuansCount); // => 431.875JavaScript will easily evaluate this expression. But it is no longer convenient for a human to read such code. Questions immediately arise:
- What does
1.25mean? - What does
6.91mean? - Where does one calculation step end and the next begin?
To make such calculations clearer, variables can be used inside other expressions. First the program saves an intermediate result in a variable, and then it substitutes the value of that variable into the next calculation.
Expressions
Any computable value is an expression. You can assign an expression to a variable, not just a ready-made value.
const sum = 3 + 4; // => 7
const text = 'Hello' + '!'; // => 'Hello!'
const doubled = sum * 2; // => 14JavaScript first evaluates the expression to the right of =, and then saves the result in the variable on the left.
Currency conversion through an intermediate currency
Imagine we need to convert euros to yuan, but the direct rate is not available to us. Then we will do it in two steps: euros → dollars → yuan. This is often how banks work when paying for purchases abroad.
Step 1. Euros → Dollars
Suppose the rate is: 1 euro = 1.25 dollars. We want to convert 50 euros:
const dollarsPerEuro = 1.25;
const dollarsCount = 50 * dollarsPerEuro;
console.log(dollarsCount); // => 62.5In this line, 50 * dollarsPerEuro is an expression, and dollarsCount is the variable into which the result is written. JavaScript first evaluates the expression, and only then saves the result in the variable.
The engine does not care how the expression is written:
const dollarsCount = 62.5;or
const dollarsCount = 50 * dollarsPerEuro;The result will be the same. But for a human the second option is more useful: from the name dollarsCount it is immediately clear that at this step we got the amount in dollars.
Step 2. Dollars → Yuan
Now let's convert 50 euros to yuan, using the dollar as an intermediate currency. Suppose the exchange rates are: 1 dollar = 6.91 yuan, 1 euro = 1.25 dollars.
const dollarsPerEuro = 1.25;
const yuansPerDollar = 6.91;
const dollarsCount = 50 * dollarsPerEuro;
const yuansCount = dollarsCount * yuansPerDollar;
console.log(yuansCount);This code is longer than the single line 50 * 1.25 * 6.91, but it is easier to read:
- you can see that
1.25is the euro-to-dollar rate; - you can see that
6.91is the dollar-to-yuan rate; - you can see that
dollarsCountis an intermediate result.
This becomes especially noticeable if you don't come back to the code for at least a week. And now imagine that a project has hundreds of thousands of lines of code. If such projects had no intermediate variables and calculations, it would be impossible to make sense of them.
What to remember
- If an expression turns out to be too long, it is better to break it into several steps.
- Variables help save intermediate results and make calculations clearer.
- When a variable is used in an expression, JavaScript substitutes its value and continues the calculation.
Instructions
Given the number of euros: eurosCount = 100. Write a program that:
- Converts euros to dollars at the rate of
1.25and prints the result. - Converts dollars to yuan at the rate of
6.91and prints the result.
Use variables to store the intermediate values.
Tips
If you've reached a deadlock it's time to ask your question in the «Discussions». How ask a question correctly:
- Be sure to attach the test output, without it it's almost impossible to figure out what went wrong, even if you show your code. It's complicated for developers to execute code in their heads, but having a mistake before their eyes most probably will be helpful.
Tests are designed so that they test the solution in different ways and against different data. Often the solution works with one kind of input data but doesn't work with others. Check the «Tests» tab to figure this out, you can find hints at the error output.
It's fine. 🙆 One task in programming can be solved in many different ways. If your code passed all tests, it complies with the task conditions.
In some rare cases, the solution may be adjusted to the tests, but this can be seen immediately.
It's hard to make educational materials that will suit everyone. We do our best but there is always something to improve. If you see a material that is not clear to you, describe the problem in “Discussions”. It will be great if you'll write unclear points in the question form. Usually, we need a few days for corrections.
By the way, you can participate in courses improvement. There is a link below to the lessons course code which you can edit right in your browser.
Создавать обучающие материалы, понятные для всех без исключения, довольно сложно. Мы очень стараемся, но всегда есть что улучшать. Если вы встретили материал, который вам непонятен, опишите проблему в обратной связи нашего сообщества
Your exercise will be checked with these tests:
// @ts-check
import { expect, test, vi } from 'vitest';
test('hello world', async () => {
const consoleLogSpy = vi.spyOn(console, 'log').mockImplementation(() => {});
await import('./index.js');
const firstArg = consoleLogSpy.mock.calls.join('\n');
expect(firstArg).toBe('125\n863.75');
});Teacher's solution will be available in:
20:00
