Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
More often than not, you're going to get bugs.
So it helps to visualize the runtime using breakpoints in this lesson, you're going to learn how to
use breakpoints.
You can access this lesson from the resources if your resources don't include the following path, then
please download the updated resources from GitHub.
All right, inside the breakpoints class, we can start a debugging session to visualize the output
of each variable line by line.
So in this code, click the run and debug option.
And click on credit lines that Jason file, and here you can see the current file that we can launch
the debugger for, it's the file that corresponds to the breakpoints class.
Not that important, just showing you what's going on behind the scenes.
But what we want to do is we're going to place a breakpoint next to each line of code when we launch
the debugger for this file.
What it's going to do is it's going to stop at each break point and allow us to visualize the output
for that line.
Essentially, it's going to allow us to visualize the run time line by line, kind of like the animations
I've been showing you throughout the course, except now we can do it in voice code, which is really
cool.
So without further ado, click launch.
Current file.
Press continue to stop at each breakpoint.
And here in the left pane, you can visualize the output of each variable and long double boolean car
are primitive types and notice that each primitive store is a value.
And once you get to the last break point, if you press continue, it's just going to disappear because
debugging session is over.
So let's restart the session.
Go to the last line.
And a small little trick for you is to step over at the last line if you want to see it.
Now, string is a class type, you can see that the string variable contains an object with a bunch
of fields'.
One of the fields is an array that contains the ASCII representation of each character.
So what you would see is hello, but what's actually being stored is one hundred and four one two one
one.
Oh, wait.
Where each one corresponds to a character.
Again, this isn't that important.
It's just really cool that this code allows us to see exactly how each variable behaves.
In this lesson, you learn to visualize the output of a variable.
You visualized five primitives, each one stores of value, and you visualize the class type variable
which contains an object.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.