3 ms·

I didn’t respond regarding Algol because you said nothing of immediate relevance requiring a response. I’m familiar with the history of Algol 60. I’m not intere

by User23 4y ago

I didn’t respond regarding Algol because you said nothing of immediate relevance requiring a response. I’m familiar with the history of Algol 60. I’m not interested in regurgitating wikipedia with you. Here[1] is a good primary source on the history of programming and significance of Algol in context for you to read. Note that call/return is nowhere mentioned. Stop chasing tangents and address your core misunderstanding. Algorithms are not call and return. [1] https://www.cs.utexas.edu/users/EWD/transcriptions/EWD10xx/EWD1024.html https://www.cs.utexas.edu/users/EWD/transcriptions/EWD10xx/E...

mpweiher 4y ago
OK, thanks for clarifying that you did not understand what I wrote in the least bit and have no intention of learning, not even so far as looking at the relevant information on Wikipedia, which would help clear up your misunderstandings. Once again: ALGOL is the ALGOrithmic Language. It might have something to do with algorithms. Now please tell me what the main structuring mechanism for code is in Algol (and C, for that matter). Do you at least understand that any language derived from C is therefore also derived from ALGOL? And nobody claimed that Algorithms "are" call/return. They are just intricately related in both history and current practice, particularly once we stopped treating "primitive" operations separately and instead started understanding them as functions/procedures as well. (In C, something like multiplication is considered an operation (via the * operator), whereas most current languages treat multiplication is considered a function that the compiler understands and will directly emit machine code for). So please stop chasing tangents that have nothing to do with what I wrote and what I've done and address your core misunderstanding(s). Have a good one.
- User23 4y ago
  - dang 4y ago
    If you keep posting like this, we will ban you. Please see https://news.ycombinator.com/item?id=32466681 https://news.ycombinator.com/item?id=32466681.
- dang 4y ago
  Can you please stop breaking the site guidelines? This sort of tit-for-tat flamewar is not ok. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html

by User23 4y ago

mpweiher 4y ago

OK, thanks for clarifying that you did not understand what I wrote in the least bit and have no intention of learning, not even so far as looking at the relevant information on Wikipedia, which would help clear up your misunderstandings. Once again: ALGOL is the ALGOrithmic Language. It might have something to do with algorithms. Now please tell me what the main structuring mechanism for code is in Algol (and C, for that matter). Do you at least understand that any language derived from C is therefore also derived from ALGOL? And nobody claimed that Algorithms "are" call/return. They are just intricately related in both history and current practice, particularly once we stopped treating "primitive" operations separately and instead started understanding them as functions/procedures as well. (In C, something like multiplication is considered an operation (via the * operator), whereas most current languages treat multiplication is considered a function that the compiler understands and will directly emit machine code for). So please stop chasing tangents that have nothing to do with what I wrote and what I've done and address your core misunderstanding(s). Have a good one.

User23 4y ago
- dang 4y ago
  If you keep posting like this, we will ban you. Please see https://news.ycombinator.com/item?id=32466681 https://news.ycombinator.com/item?id=32466681.
dang 4y ago
Can you please stop breaking the site guidelines? This sort of tit-for-tat flamewar is not ok. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html