G - Revision history

Logmanoriginal: Cleanup and add additional links

2019-08-16T17:35:46Z

Cleanup and add additional links

← Older revision		Revision as of 17:35, 16 August 2019
Line 1:		Line 1:
	G ~~is the "native~~" ~~language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called~~ G ~~source code. Let it therefore be said that strictly speaking LabVIEW~~ is ~~the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into~~ a ~~text based~~ language~~. You cannot pop the hood on LabVIEW generated code~~ and ~~see the underlying text code, because there is none! Thus G remains the underlying source code that~~ LabVIEW ~~developers work with.~~.		"G" ('''G''' Dataflow) is a proprietary [[Data flow\|dataflow]] programming language owned by [[National Instruments]] and used in [[LabVIEW]].

	== See ~~Also~~ ==		== G versus LabVIEW ==
	[[Getting Started]]
			Strictly speaking LabVIEW is the development environment, while "G" is the source code produced in LabVIEW. However, due to the fact that LabVIEW is the only environment supporting "G" as a programming language, the source code is often called LabVIEW code rather than "G" code <ref>[https://trends.google.com/trends/explore?q=%22LabVIEW%22,%22G%22%20(LabVIEW) Comparing "LabVIEW" to "G" (LabVIEW)] (Google Trends)</ref>.

			== See also ==
			* [[Getting Started]]

			== External links ==
			* [http://www.ni.com/documentation/en/labview/latest/g-prog/dataflow/ LabVIEW NXG 3.1 Manual - G Dataflow] (National Instruments)

			== References ==
			<references />

	[[Category:LabVIEW fundamentals]]		[[Category:LabVIEW fundamentals]]

Testaccount at 08:20, 7 November 2018

2018-11-07T08:20:33Z

← Older revision		Revision as of 08:20, 7 November 2018
Line 1:		Line 1:
	G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVIEW is the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into a text based language. You cannot pop the hood on LabVIEW generated code and see the underlying text code, because there is none! Thus G remains the underlying source code that LabVIEW developers work with.		G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVIEW is the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into a text based language. You cannot pop the hood on LabVIEW generated code and see the underlying text code, because there is none! Thus G remains the underlying source code that LabVIEW developers work with..

	== See Also ==		== See Also ==

MichaelAivaliotis at 08:39, 13 July 2009

2009-07-13T08:39:00Z

← Older revision		Revision as of 08:39, 13 July 2009
Line 2:		Line 2:

	== See Also ==		== See Also ==
	~~{{Portal\|~~Getting Started}}		[[Getting Started]]

	[[~~category~~:LabVIEW fundamentals]]		[[Category:LabVIEW fundamentals]]

Michael_Aivaliotis at 09:37, 8 October 2007

2007-10-08T09:37:07Z

← Older revision		Revision as of 09:37, 8 October 2007
Line 1:		Line 1:
	G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVIEW is the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into a text based language. You cannot pop the hood on LabVIEW generated code and see the underlying text code, because there is none! Thus G remains the underlying source code that LabVIEW developers work with.		G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVIEW is the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into a text based language. You cannot pop the hood on LabVIEW generated code and see the underlying text code, because there is none! Thus G remains the underlying source code that LabVIEW developers work with.

	== See Also ==		== See Also ==
	{{Portal\|Getting Started}}		{{Portal\|Getting Started}}

			[[category:LabVIEW fundamentals]]

Michael_Aivaliotis at 08:49, 1 October 2007

2007-10-01T08:49:56Z

← Older revision		Revision as of 08:49, 1 October 2007
Line 2:		Line 2:
	== See Also ==		== See Also ==
	{{Portal\|Getting Started}}		{{Portal\|Getting Started}}

	~~[[Category:Uncategorized]]~~

MichaelAivaliotis at 10:11, 3 April 2007

2007-04-03T10:11:41Z

← Older revision		Revision as of 10:11, 3 April 2007
Line 2:		Line 2:
	== See Also ==		== See Also ==
	{{Portal\|Getting Started}}		{{Portal\|Getting Started}}

			[[Category:Uncategorized]]

MichaelAivaliotis at 08:42, 19 March 2007

2007-03-19T08:42:55Z

← Older revision		Revision as of 08:42, 19 March 2007
Line 1:		Line 1:
	G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVIEW is the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into a text based language. You cannot pop the hood on LabVIEW generated code and see the underlying text code, because there is none! Thus G remains the underlying source code that LabVIEW developers work with.		G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVIEW is the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into a text based language. You cannot pop the hood on LabVIEW generated code and see the underlying text code, because there is none! Thus G remains the underlying source code that LabVIEW developers work with.
			== See Also ==
			{{Portal\|Getting Started}}

MichaelAivaliotis: New page: G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVI...

2007-03-18T00:47:59Z

New page: G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVI...

New page

G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVIEW is the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into a text based language. You cannot pop the hood on LabVIEW generated code and see the underlying text code, because there is none! Thus G remains the underlying source code that LabVIEW developers work with.