<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://labviewwiki.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Testaccount</id>
	<title>LabVIEW Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://labviewwiki.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Testaccount"/>
	<link rel="alternate" type="text/html" href="https://labviewwiki.org/wiki/Special:Contributions/Testaccount"/>
	<updated>2026-05-06T02:30:31Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://labviewwiki.org/w/index.php?title=G&amp;diff=5416</id>
		<title>G</title>
		<link rel="alternate" type="text/html" href="https://labviewwiki.org/w/index.php?title=G&amp;diff=5416"/>
		<updated>2018-11-07T08:20:33Z</updated>

		<summary type="html">&lt;p&gt;Testaccount: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;G is the &amp;quot;native&amp;quot; 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..&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
[[Getting Started]]&lt;br /&gt;
&lt;br /&gt;
[[Category:LabVIEW fundamentals]]&lt;/div&gt;</summary>
		<author><name>Testaccount</name></author>
	</entry>
</feed>