Manidh: 1 revision imported

2023-07-26T05:32:59Z

1 revision imported

← Older revision	Revision as of 11:02, 26 July 2023
(No difference)

wikipedia>W.andrea: Revert insertion of another lead section. Some parts may be worth adding back, but others are incorrect, repetitive, or redundant.

2023-07-26T02:21:33Z

Revert insertion of another lead section. Some parts may be worth adding back, but others are incorrect, repetitive, or redundant.

New page

A '''method stub''' or simply '''stub'''<ref name="DaleWeems2004">{{cite book|author1=Nell B. Dale|author2=Chip Weems|title=Programming in C++|url=https://books.google.com/books?id=mxZBPSjSEYUC&pg=PA308|year=2004|publisher=Jones & Bartlett Learning|isbn=978-0-7637-3234-9|pages=308}}</ref> in [[software development]] is a piece of code used to stand in for some other programming functionality. A stub may [[simulation|simulate]] the behavior of existing code (such as a [[Subroutine|procedure]] on a remote machine; such methods are often called mocks) or be a temporary substitute for yet-to-be-developed code. Stubs are therefore most useful in [[porting]], [[distributed computing]] as well as general software development and [[Software testing|testing]].

An example of a stub in [[pseudocode]] might be as follows:

temperature = ThermometerRead(Outside)
'''if''' temperature > 40 '''then'''
print "It is hot!"
'''end if'''

'''function''' ThermometerRead(Source insideOrOutside)
'''return''' 28
'''end function'''

The above pseudocode utilises the function {{mono|ThermometerRead}}, which returns a temperature. While {{mono|ThermometerRead}} would be intended to read some hardware device, this function currently does not contain the necessary code. So {{mono|ThermometerRead}} does not, in essence, [[Simulation|simulate]] any process, yet it ''does'' return a legal value, allowing the main program to be at least partially tested. Although it accepts the [[Parameter (computer science)|parameter]] of type {{mono|Source}}, which determines whether inside or outside temperature is needed, it does not use the actual value passed ([[Argument (computer science)|argument]] {{mono|insideOrOutside}}) by the caller in its logic.

A stub <ref>{{cite web
| url = http://www.webopedia.com/TERM/S/stub.html
| title = stub
| date = 23 March 1998
| publisher = WEBOPEDIA
| quote =
| accessdate = 2012-08-28
}}</ref> is a routine that doesn't actually do anything other than declaring itself and the parameters it accepts and returning something that is usually the values expected in one of the "happy scenarios" for the caller. Stubs are used commonly as placeholders for implementation of a known interface, where the [[interface (computer science)|interface]] is finalized/known but the implementation is not yet known/finalized. The stub contains just enough code to allow it to be compiled and linked with the rest of the program. In [[Remote Method Invocation|RMI]] nomenclature, a stub on the client-side communicates with a [[Skeleton (computer science)|skeleton]] on the server-side.<ref>{{cite book
| last1 = Freeman
| first1 = Eric
| authorlink1 =
| last2 = Freeman
| first2 = Elisabeth
| authorlink2 =
| last3 = Kathy
| first3 = Sierra
| authorlink3 =
| last4 = Bert
| first4 = Bates
| authorlink4 =
| editor1-last = Hendrickson
| editor1-first = Mike
| editor2-last = Loukides
| editor2-first = Mike
| year = 2004
| title = Head First Design Patterns
| volume = 1
| page = 440
| publisher = O'REILLY
| format = paperback
| isbn = 978-0-596-00712-6
| accessdate = 2012-08-28
| url = http://shop.oreilly.com/product/9780596007126.do
}}</ref>

In the context of [[DOS]] and [[Windows]], the term ''stub'' is also used in a fashion like [[Shim (computing)|shim]] to describe the small areas of interface code left in [[conventional memory]] by [[self-relocation|self-relocating]] resident drivers which move most of themselves into [[upper memory]], the [[high memory area]], [[expanded memory|expanded]] or [[extended memory]] as well as similar stubs to allow the relocated code to communicate with [[real-mode]] DOS in conjunction with [[DOS extender]]s (like [[DOS Protected Mode Interface|DPMI]], [[DOS Protected Mode Services|DPMS]], [[CLOAKING (DOS extender)|CLOAKING]] or [[NetWare I/O Subsystem|NIOS]]).

The small pieces of dummy code branched into—so as to allow a graceful exit when invoking a [[fat binary]] in the wrong environment—are also called (code) stubs.

== See also ==

* [[Method (computer science)#Abstract methods|Abstract method]]
* [[Mock object]]
* [[Dummy code]]
* [[Test stub]]
* [[Glue code]]
* [[Shim (computing)]]
* [[DOS stub]]

== References ==
{{reflist}}

== External links ==
* [http://www.cs.ncl.ac.uk/research/pubs/articles/papers/94.pdf A Stub Generation System For C++] (PDF)
* [https://web.archive.org/web/20090711150137/http://www.sizovpoint.com/2009/03/java-mock-frameworks-comparison.html Stub/mock frameworks for Java] Review and comparison of stub & mock frameworks for Java




[[Category:Unit testing]]
[[Category:Computer programming folklore]]
[[Category:Software development]]

Method stub - Revision history

Manidh: 1 revision imported

wikipedia>W.andrea: Revert insertion of another lead section. Some parts may be worth adding back, but others are incorrect, repetitive, or redundant.