YouTube

Got a YouTube account?

New: enable viewer-created translations and captions on your YouTube channel!

English subtitles

← Part 3

Get Embed Code
2 Languages

Showing Revision 3 created 05/24/2016 by Udacity Robot.

  1. Okay let me get back to where I was.
  2. Okay, so we declared the two variables, and then there's two print lines
  3. the first one >> Excuse me did, did the recorder correct the comments?
  4. To make, make note of the errors in the comments that,
  5. that >> Slash asterisk should our new standard coding as well.
  6. >> Yeah these easier being pointed out, that we should be,
  7. it's said that they're characters but they were declared as integers.
  8. >> For int next, it says next character is that it?
  9. >> Yeah. >> Put a line through.
  10. >> The implication is that you're confused about characters versus integers.
  11. >> Mm-hm, even though the representation was also signed.
  12. >> Okay so as I was saying there is two print statement,
  13. the first one prints to the user, enter a sentence ending with a period, and
  14. the second one says, follow each character buy a return.
  15. >> We have a typo.
  16. >> Yeah, I guess, buy should not really be buy, >> And
  17. also probably, follow, should be capitalized, right?
  18. I mean it's a separate sentence so
  19. you're trying to [COUGH] write it as a sentence.
  20. >> Or it should be all on one line, because you're,
  21. you're breaking at interest and it's ending with a period oh, okay, I see.
  22. >> But it also, it's interesting,
  23. Interest in it is ending with a period doesn't have a delimiter at
  24. the end where it's follow each character by a return does have a delimiter.
  25. >> Should that be, have a colon there?
  26. >> It seems like we're really getting stuck on minor details.
  27. >> I think so too, let's move on, let's move on back to Dr.
  28. Bug, please continue.
  29. >> So a character is, misspelled.
  30. >> It's charcter.
  31. >> Just making, I think it's making for bad user experience, we don't, we don't,
  32. you know >> Yeah, actually I think I was just copy and
  33. paste in here from someone elses code, but that's fine.
  34. Yeah, I think it's. [LAUGH] >> Is that what we do now?
  35. Is we copy, copy from other people's [CROSSTALK].
  36. >> Well, it's just this, you know?
  37. This was [CROSSTALK].
  38. >> Whose was it that we copied from?
  39. >> It was part of a log, I mean, I think it was actually Crazy Bob's code, but
  40. [LAUGH] I could be wrong.
  41. >> It wasn't my code because it's not in native.
  42. [LAUGH] >> Yeah. >> It was a native piece of code.
  43. >> In fact, if we could just back go back and revisit, 13 and
  44. 14, you know, this initialization problem wouldn't even be
  45. occurring because you can't have uninitialized data in aid.
  46. So if we'd actually done what we said,
  47. what I said originally, we wouldn't be having these problems.
  48. >> You, you're absolutely right, I forgot about that.
  49. Crazy Bob bring,
  50. brings up some excellent points, about this lousy code we're looking at.
  51. >> I have to say, actually, I'm pretty sure that in Java, when you
  52. declare a lock of variable like this, it gets initialized automatically to zero.
  53. But I might be wrong.
  54. >> That's the instance variables that are initialized, and
  55. the local variables are not initialized.
  56. >> Okay, maybe I'm wrong then >> Even if there are automatically initialized,
  57. good code behavior would be that you actually initialize them so
  58. everybody doesn't have to remember whether it works or not.
  59. >> Well, just, you know, I was used to developing data, so that's reality.
  60. >> Yeah [LAUGH].
  61. >> Okay, let us continue Dr. Bug.