Object-oriented programming - Revision history

Logmanoriginal: Add link to Template pattern

2024-08-08T14:14:41Z

← Older revision		Revision as of 14:14, 8 August 2024
Line 24:		Line 24:
	* Specification pattern		* Specification pattern
	* Strategy pattern (aka. Policy pattern)		* Strategy pattern (aka. Policy pattern)
	* Template ~~method~~ pattern (aka. Channeling pattern)		* [[Template pattern]] (aka. Channeling pattern)
	* Visitor pattern		* Visitor pattern
	See also: [[:Category:Object-Oriented Design Pattern]]s		See also: [[:Category:Object-Oriented Design Pattern]]s

Logmanoriginal: /* Object-Oriented Programming in LabVIEW */ Add list of design patterns

2020-04-12T18:42:02Z

Object-Oriented Programming in LabVIEW: Add list of design patterns

← Older revision		Revision as of 18:42, 12 April 2020
Line 13:		Line 13:

	G supports single inheritance in which a class can have only one parent. Children inherit public and protected methods from their parent and can override inherited dynamic dispatch methods. A parent class can require a descendant to override specific dynamic dispatch methods and to call the parent method from inside the override.		G supports single inheritance in which a class can have only one parent. Children inherit public and protected methods from their parent and can override inherited dynamic dispatch methods. A parent class can require a descendant to override specific dynamic dispatch methods and to call the parent method from inside the override.

			Many common object-oriented design patterns have been adapted into the by-value dataflow in G.
			* [[Aggregation pattern]]
			* [[Command pattern]]
			* [[Decorator pattern]] (aka. Wrapper pattern)
			* [[Delegation (object-oriented programming)\|Delegation]] (aka. Delegation pattern)
			* [[Factory pattern]]
			* Hierarchy composition pattern
			* Singleton pattern
			* Specification pattern
			* Strategy pattern (aka. Policy pattern)
			* Template method pattern (aka. Channeling pattern)
			* Visitor pattern
			See also: [[:Category:Object-Oriented Design Pattern]]s

	==Benefits of OOP==		==Benefits of OOP==

Logmanoriginal: /* Object-Oriented Programming in LabVIEW */ Fix typo

2020-04-06T10:23:42Z

Object-Oriented Programming in LabVIEW: Fix typo

← Older revision		Revision as of 10:23, 6 April 2020
Line 8:		Line 8:
	As of [[LabVIEW 8.20]], [[G]] is an object-oriented programming language that enforces object-oriented design principles.		As of [[LabVIEW 8.20]], [[G]] is an object-oriented programming language that enforces object-oriented design principles.

	A ~~Class~~ is defined by a [[class library]] that serves as a user-defined data type. Each class consists of a private data control and methods (member VIs) to access that data. A class can change the [[access scope]] of its methods to public (anyone), protected (this class and its descendants), community (this class and its friends) or private (this class).		A class is defined by a [[class library]] that serves as a user-defined data type. Each class consists of a private data control and methods (member VIs) to access that data. A class can change the [[access scope]] of its methods to public (anyone), protected (this class and its descendants), community (this class and its friends) or private (this class).

	An object is a specific instance of a class. It is represented by data on a wire and behaves like a [[cluster]]. Objects in G are by-value. When a wire forks, the object may be duplicated, as decided by the [[LabVIEW compiler]]. A wire of a specific class can carry an object of that class or any of its descendants without loss of data.		An object is a specific instance of a class. It is represented by data on a wire and behaves like a [[cluster]]. Objects in G are by-value. When a wire forks, the object may be duplicated, as decided by the [[LabVIEW compiler]]. A wire of a specific class can carry an object of that class or any of its descendants without loss of data.

Logmanoriginal: Add OOP in LabVIEW

2020-04-04T20:08:27Z

Add OOP in LabVIEW

← Older revision		Revision as of 20:08, 4 April 2020
Line 1:		Line 1:
	'''Object-Oriented Programming''' (OOP) is a [[Wikipedia:programming paradigm\|programming paradigm]] that enforces [[Wikipedia:object-oriented design\|object-oriented design]] principles to solve software problems~~. As of [[LabVIEW 8.20]], LabVIEW is an object-oriented programming language~~. In object-oriented programming, a [[class (object-oriented programming)\|class]] defines data ~~with restricted access,~~ and [[method (object-oriented programming)\|method]]s to work with that data. A client then creates an [[object (object-oriented programming)\|object]] - a specific instance of a class - to perform actions using methods that are exposed by the class. ~~The implementation~~ details are hidden from the client.		'''Object-Oriented Programming''' (OOP) is a [[Wikipedia:programming paradigm\|programming paradigm]] that enforces [[Wikipedia:object-oriented design\|object-oriented design]] principles to solve software problems. In object-oriented programming, a [[class (object-oriented programming)\|class]] defines data and [[method (object-oriented programming)\|method]]s to work with that data. A client then creates an [[object (object-oriented programming)\|object]] - a specific instance of a class - to perform actions using methods that are exposed by the class. Implementation details are hidden from the client.

	Because implementation details are hidden from the client, methods and data of a class can change without affecting any of the client's code. This can even happen at runtime by replacing one class with another of the same kind. Classes can [[inheritance\|inherit]] methods and data from a parent class to [[overriding\|override]] methods of the parent class. The client can then use the child class as if it was the parent class, without changing any of the existing code. Methods called by the client will seamlessly execute the methods defined by the child class. If the child class doesn't override a method, the parent's method is called. This behavior is called [[dynamic dispatching]] in LabVIEW.		Because implementation details are hidden from the client, methods and data of a class can change without affecting any of the client's code. This can even happen at runtime by replacing one class with another of the same kind. Classes can [[inheritance\|inherit]] methods and data from a parent class to [[overriding\|override]] methods of the parent class. The client can then use the child class as if it was the parent class, without changing any of the existing code. Methods called by the client will seamlessly execute the methods defined by the child class. If the child class doesn't override a method, the parent's method is called. This behavior is called [[dynamic dispatching]] in LabVIEW.
Line 5:		Line 5:
	[[File:OOP Example.png]]		[[File:OOP Example.png]]

	A ~~parent~~ class can change the [[access scope]] of ~~a method to limit access~~ to ~~child classes~~ (protected), friends ~~(community~~) or ~~nobody~~ (~~private~~). ~~Public methods~~ are ~~accessible~~ by ~~anyone~~.		==Object-Oriented Programming in LabVIEW==
			As of [[LabVIEW 8.20]], [[G]] is an object-oriented programming language that enforces object-oriented design principles.

			A Class is defined by a [[class library]] that serves as a user-defined data type. Each class consists of a private data control and methods (member VIs) to access that data. A class can change the [[access scope]] of its methods to public (anyone), protected (this class and its descendants), community (this class and its friends) or private (this class).

			An object is a specific instance of a class. It is represented by data on a wire and behaves like a [[cluster]]. Objects in G are by-value. When a wire forks, the object may be duplicated, as decided by the [[LabVIEW compiler]]. A wire of a specific class can carry an object of that class or any of its descendants without loss of data.

			G supports single inheritance in which a class can have only one parent. Children inherit public and protected methods from their parent and can override inherited dynamic dispatch methods. A parent class can require a descendant to override specific dynamic dispatch methods and to call the parent method from inside the override.

	==Benefits of OOP==		==Benefits of OOP==

Logmanoriginal: /* See also */ Add link to FAQ

2020-04-02T14:56:41Z

Logmanoriginal: /* See also */ Update and extend links

2020-04-02T14:28:34Z

Logmanoriginal: /* External links */ Update and extend links

2020-04-02T14:06:51Z

External links: Update and extend links

← Older revision		Revision as of 14:06, 2 April 2020
Line 18:		Line 18:

	==External links==		==External links==
	* [~~[Wikipedia~~:~~Object~~-oriented ~~design\|~~Object-~~oriented design]~~] ~~(Wikipedia)~~		*[https://www.ni.com/en-us/support/documentation/supplemental/06/labview-object-oriented-programming-faq.html LabVIEW Object-Oriented Programming FAQ] by National Instruments
	* [~~[Wikipedia~~:~~SOLID\|SOLID~~]~~] (Wikipedia)~~		*[https://www.ni.com/en-us/support/documentation/supplemental/06/labview-object-oriented-programming--the-decisions-behind-the-de.html LabVIEW Object-Oriented Programming: The Decisions Behind the Design] by National Instruments
	*[http://www.ni.com/~~white-paper~~/~~3573~~/en/ ~~NI FAQ on Object Oriented Programming~~]		*[http://www.eyesonvis.com/blog/2006/08/code-reuse-through-classes.html Code Reuse through Classes] by Christina Rogers
	*[https://forums.ni.com/t5/LabVIEW-Development-Best/Introduction-to-Object-Oriented-Programming-and-Hardware/ta-p/3519580 Introduction to Object Oriented Programming] by Elijah Kerry		*[https://forums.ni.com/t5/LabVIEW-Development-Best/Introduction-to-Object-Oriented-Programming-and-Hardware/ta-p/3519580 Introduction to Object Oriented Programming] by Elijah Kerry
	*[http://zone.ni.com/reference/en-XX/help/371361P-01/lvconcepts/creating_classes/ Creating Classes]		*[https://forums.ni.com/t5/LabVIEW-Development-Best/When-Should-You-Use-LabVIEW-Classes/ba-p/3478257 When should you use classes] by Elijah Kerry
	*[https://forums.ni.com/t5/LabVIEW-Development-Best/When-Should-You-Use-LabVIEW-Classes/ba-p/3478257 When should you use classes]

	{{stub}}		{{stub}}

Logmanoriginal: Add an example to illustrate dynamic dispatching

2020-04-01T15:45:47Z

Add an example to illustrate dynamic dispatching

← Older revision		Revision as of 15:45, 1 April 2020
Line 2:		Line 2:

	Because implementation details are hidden from the client, methods and data of a class can change without affecting any of the client's code. This can even happen at runtime by replacing one class with another of the same kind. Classes can [[inheritance\|inherit]] methods and data from a parent class to [[overriding\|override]] methods of the parent class. The client can then use the child class as if it was the parent class, without changing any of the existing code. Methods called by the client will seamlessly execute the methods defined by the child class. If the child class doesn't override a method, the parent's method is called. This behavior is called [[dynamic dispatching]] in LabVIEW.		Because implementation details are hidden from the client, methods and data of a class can change without affecting any of the client's code. This can even happen at runtime by replacing one class with another of the same kind. Classes can [[inheritance\|inherit]] methods and data from a parent class to [[overriding\|override]] methods of the parent class. The client can then use the child class as if it was the parent class, without changing any of the existing code. Methods called by the client will seamlessly execute the methods defined by the child class. If the child class doesn't override a method, the parent's method is called. This behavior is called [[dynamic dispatching]] in LabVIEW.

			[[File:OOP Example.png]]

	A parent class can change the [[access scope]] of a method to limit access to child classes (protected), friends (community) or nobody (private). Public methods are accessible by anyone.		A parent class can change the [[access scope]] of a method to limit access to child classes (protected), friends (community) or nobody (private). Public methods are accessible by anyone.

Logmanoriginal: Disambiguate links for class, method and object.

2020-04-01T14:19:58Z

Disambiguate links for class, method and object.

← Older revision		Revision as of 14:19, 1 April 2020
Line 1:		Line 1:
	'''Object-Oriented Programming''' (OOP) is a [[Wikipedia:programming paradigm\|programming paradigm]] that enforces [[Wikipedia:object-oriented design\|object-oriented design]] principles to solve software problems. As of [[LabVIEW 8.20]], LabVIEW is an object-oriented programming language. In object-oriented programming, a [[class]] defines data with restricted access, and [[method]]s to work with that data. A client then creates an [[object]] - a specific instance of a class - to perform actions using methods that are exposed by the class. The implementation details are hidden from the client.		'''Object-Oriented Programming''' (OOP) is a [[Wikipedia:programming paradigm\|programming paradigm]] that enforces [[Wikipedia:object-oriented design\|object-oriented design]] principles to solve software problems. As of [[LabVIEW 8.20]], LabVIEW is an object-oriented programming language. In object-oriented programming, a [[class (object-oriented programming)\|class]] defines data with restricted access, and [[method (object-oriented programming)\|method]]s to work with that data. A client then creates an [[object (object-oriented programming)\|object]] - a specific instance of a class - to perform actions using methods that are exposed by the class. The implementation details are hidden from the client.

	Because implementation details are hidden from the client, methods and data of a class can change without affecting any of the client's code. This can even happen at runtime by replacing one class with another of the same kind. Classes can [[inheritance\|inherit]] methods and data from a parent class to [[overriding\|override]] methods of the parent class. The client can then use the child class as if it was the parent class, without changing any of the existing code. Methods called by the client will seamlessly execute the methods defined by the child class. If the child class doesn't override a method, the parent's method is called. This behavior is called [[dynamic dispatching]] in LabVIEW.		Because implementation details are hidden from the client, methods and data of a class can change without affecting any of the client's code. This can even happen at runtime by replacing one class with another of the same kind. Classes can [[inheritance\|inherit]] methods and data from a parent class to [[overriding\|override]] methods of the parent class. The client can then use the child class as if it was the parent class, without changing any of the existing code. Methods called by the client will seamlessly execute the methods defined by the child class. If the child class doesn't override a method, the parent's method is called. This behavior is called [[dynamic dispatching]] in LabVIEW.

Logmanoriginal: Logmanoriginal moved page Object oriented software to Object-oriented programming: This article describes object-orienting programming as a principle

2020-03-31T17:08:41Z

Logmanoriginal moved page Object oriented software to Object-oriented programming: This article describes object-orienting programming as a principle

← Older revision	Revision as of 17:08, 31 March 2020
(No difference)

← Older revision		Revision as of 14:56, 2 April 2020
Line 14:		Line 14:
	* [[LabVIEW Class]]		* [[LabVIEW Class]]
	* [[LabVIEW Object]]		* [[LabVIEW Object]]
			* [[LabVIEW object-oriented programming FAQ]]
	* [[Americas CLA Summit 2019#StephenGInterfaces\|Americas CLA Summit 2019: G Interfaces]] by Stephen Loftus-Mercer		* [[Americas CLA Summit 2019#StephenGInterfaces\|Americas CLA Summit 2019: G Interfaces]] by Stephen Loftus-Mercer
	* [[Graphical Object-Oriented Programming]] (GOOP)		* [[Graphical Object-Oriented Programming]] (GOOP)

← Older revision		Revision as of 14:28, 2 April 2020
Line 12:		Line 12:

	==See also==		==See also==
	* [[~~LVClass~~]]		* [[LabVIEW Class]]
	* [[~~G-sharp Framework]]~~		* [[LabVIEW Object]]
	* [[GOOP]]		* [[Americas CLA Summit 2019#StephenGInterfaces\|Americas CLA Summit 2019: G Interfaces]] by Stephen Loftus-Mercer
	* [[Americas CLA Summit 2019#StephenGInterfaces\|Stephen Loftus-Mercer ~~ACLA Summit 2019 Presentation on~~ G ~~Interfaces~~]]		* [[Graphical Object-Oriented Programming]] (GOOP)
			* [[G-sharp Framework\|G# Framework]]

	==External links==		==External links==