Talk:Callback (computer programming): Difference between revisions

Content deleted Content added
 
(4 intermediate revisions by 3 users not shown)
Line 104:
 
:Too many platform specific references, ie Linux, Unix. Needs to be abstracted away from punks/hackers prosaic tendencies and their favorite languages and towards compsci academics. <span style="font-size: smaller;" class="autosigned">—Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/71.15.154.180|71.15.154.180]] ([[User talk:71.15.154.180|talk]]) 04:37, 28 July 2010 (UTC)</span><!-- Template:UnsignedIP --> <!--Autosigned by SineBot-->
:LOL [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 13:58, 11 April 2024 (UTC)
 
== <nowiki></nowiki> ==
Line 225 ⟶ 226:
:I agree, it is part of the expected and well-typed way of defining callbacks in C#. [[User:Rp|Rp]] ([[User talk:Rp|talk]]) 13:39, 2 December 2019 (UTC)
:You are not ''directly'' asking a question or proposing something. I suggest a more direct approach; otherwise your comment will not result in action. IMO, the best way to get action on WP (any wiki) is to roll up your sleaves and edit. [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 13:43, 11 April 2024 (UTC)
 
== Sorry, I couldn't resist and edited page ==
 
You don't understand what it is because the term itself is misleading. (Evgeniy)--[[Special:Contributions/85.140.3.98|85.140.3.98]] ([[User talk:85.140.3.98|talk]]) 12:01, 14 September 2024 (UTC)
 
"Callback" - is noob term in [[computer programming]] into [[Abstraction (computer science)|abstraction layer]], implying supposedly a [[Function (computer programming)|function]] that sended as a parameter to another function and may be called by it. Although in fact it is not the function itself that is transferred, but only its address of ___location in memory (pointer), as a rule, this is 32-bit or 64-bit address. Calling a function means going to this address, as a rule, using the assembler command call and returning after performing all operations using the assembler command ret. Thus, this term misleads programmers, since the actual transfer of the code itself does not occur, but the transfer of the address occurs, and the call itself is not reverse, but direct.
 
:I find what you're writing difficult to follow, and I think it is too implementation specific, but I do agree that the opening sentence is confusing and needs to be changed.
:It says: ''a callback is a function that is stored as data (a reference) and designed to be called by another function – often back to the original abstraction layer.'' I have two objections to this:
:First, "a function that is stored as data (a reference)" is nonsense. Either you pass a function itself, or you pass a reference to the function; both are possible, but they are not the same thing.
:Second, what is this "original abstraction layer" doing there? Callbacks are simply a mechanism; they may or may not be used to create an abstraction layer of some kind, but no such layer needs to exist for a callback to be created.
:This is much like starting an article on ''Apple'' with the sentence: ''an apple is a fruit that is stored as organic matter (a word) and designed to be eaten by man - notably, in the creation of original sin''. No, sir or madam, either you pass an apple or you pass the word "apple", but they are not the same thing; and while passing an apple was part of the creation of original sin, apples exist completely separately from it and there is no need to mention it in the first sentence on apples. [[User:Rp|Rp]] ([[User talk:Rp|talk]]) 20:49, 16 September 2024 (UTC)