Critique of hunchbacked's "Apollo mad computer program (part 3)"

This is the last of my critiques against hunchbackeds AGC videos. Lets see if it's the final one.

Sources:

Hunchbackeds video:
http://www.youtube.com/watch?v=X_ngK7RW__Q

Users Guide to the block II AGC/LGC interpreter
http://klabs.org/history/history_docs/mit_docs/1687.pdf

AGC4 Basic Traing Manual
http://authors.library.caltech.edu/5456/1/hrst.mit.edu/hrs/apollo/public/arch...

Category:

Science & Technology

Tags:

• Apollo
• NASA
• moon
• hoax
• fake
• CM
• program
• Guidance
• Computer
• AGC
• technical
• nonsense
• hunchbacked
• critique
• conspiracy
• theory
• educational
• instructions
• electronics
• computers

[1MtnBoy]

Awesome critique ! I have attempted rational discussions with hunched for some time now hoping someday he may actually demonstrate some knowledge of facts and objective research, here's hoping ! I stink at making video's at the present, yours here is factual and splendid to watch ! only sorry I didn't see your video's sooner.

thanks for taking the time to make these video's.

[rawmonkno1]

@1MtnBoy Nice to here that you liked it 1MtnBoy. I will probably revisit this subject later with the inner working of the AGC but from a pure technical standpoint with no hoaxers involved. :)

[hunchbacked]

Tell me one thing: Imagine "TOTO+1" is a valid label, like you suggest it.

Imagine there is a label "TOTO" and a label "TOTO+1".

If there is an instruction "TCF TOTO+1", does that mean that there must be a jump to the label "TOTO+1", or to the program location one byte after the label "TOTO".

Do you see the contradiction, and the problem it may cause?

That's why there are rules for labels and data names too.

[rawmonkno1]

I already explained this, if you are going to make an arithmetic expression you need to add white spaces between the label and the expression.

"TOTO+1" is always a label.

"TOTO+1 +1" is the same label with an expression.

"TOTO +1" is another label called "TOTO" with an expression and never the same label as the one above because of the white spaces.

This is the rule and the code follows them. It's idiotic but at the same time a good way to explain a value of a constant.

[hunchbacked]

@rawmonkno1

Yes, you have explained it, but it's rules you invent, because it doesn't work this way on computers.

[rawmonkno1]

@hunchbacked I haven't invented these rules. I've actually read the documentation and looked at the code.

"because it doesn't work this way on computers"

I guess you don't understand that this is just an assembly language, it works the way it's designed to work. It doesn't matter how it works as long as it doesn't break it's own rules.

Do I actually need to continue explaining something as simple as this?

[1MtnBoy]

@rawmonkno1 Yes there have been some rather long drawn out comments on his video's, lol. I have never seen anyone make so many utterly false statements while attempting to describe AGC operation, especially Rope programs (ROM). We dissected it all the way back to "Inductive-Coupling" and still could not get him to agree on this simple electrical principle, your video shows more in 8 mins than I did in two weeks of debating with him. I could go on. lol You should do one on Rope ROM !

[philwebb59]

@hunchbacked Oops! I misread your question. I thought you repeated your question to RM1. The byte after label TOTO would be, as mercatormac said, TOTO(space)+1. A modern analogy is BASIC. If I want to append string p onto string s, I should be able to write s=s&p, but that doesn't work because if I put s in the name list, s& goes in automatically, so when the compiler lexically matches the longest string s&, then looks for an operator it sees p and bombs. & is a non-alpha, right?

[philwebb59]

@hunchbacked If as you say, instructions are one byte followed by a two byte address, then the byte after TOTO would be an address. We both know you were wrong on that one, so I would either do as RM1 described above, TOTO+1(space)+1, or create a new label. Myself, I'd create a new label and give it a descriptor associated with why I'd want to jump there. Next? BTW, where did you get the page numbers?

[mercatormac]

@hunchbacked I presume "TOTO +1" According to the documentation spaces are significant for delimiting parameters in the AGC source.

[philwebb59]

@hunchbacked Are you familiar with compiler design? Have you ever used lex and yacc to build a compiler or natural language interpreter or an sql front end to a custom database? First you put all your labels and variable names in a name list. The lexicon looks in the name list for a textual match. If TOTO+1 is in the list, then it finds a match. If not, and instead it finds TOTO, then it finds a match. Arbitration rules determine what happens if TOTO and TOTO+1 are both in the list. Next?