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
Hope you enjoyed your first debugging exercise.
The purpose of this exercise was to simply practice launching the debugger.
And so first we needed to place breakpoints next to each line where we want the runtime to stop.
So I'll go ahead and do that.
And if for some reason you're a debugger wasn't loading, then what you would just do is click on credit
lines, that JSON file.
Here we can launch the debugger for the breakpoints class, so back here we can invoke launch breakpoints
or launch current Phyll, does it really matter?
And now it helps to minimize the following windows.
And now we can visualize the run time line by line, pretty cool.
And here you can visualize the output of each declaration on the sides as well as beside each declaration.
To me, this is a lot more useful, especially when you're debugging some kind of condition.
You know, you're not sure what could go wrong.
But then when you see what the actual value is and you think to yourself, oh, OK, that's what's wrong.
So what I'm saying right now might not make a lot of sense to you, but it will once we start using
the debugger to actually debug applications.
All right.
In any case, I hope everything worked smoothly for you.
If it didn't, please ask the community on Discord.
I'm sure many other students may have had a similar problem as you and have already resolved it.
All right.
See you in the next lesson.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.