view RefPrj/Firmware/.project @ 197:c853f5d23bb7 div-fixes-cleaup-2

cleanup: fix (harmless) use before assign While looking around for possible wrong CNS values in the logbook header, I see this "interesting" thing. Simply assign the current CNS data to the global state, before using it to issue a warning. In practice, this does not fix any real bug, as the code is run very often, so the global state data is always (very) recent. It simply does not look right. Signed-off-by: Jan Mulder <jlmulder@xs4all.nl>
author Jan Mulder <jlmulder@xs4all.nl>
date Thu, 21 Mar 2019 11:41:59 +0100
parents d24395f7c939
children
line wrap: on
line source

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
	<name>OSTC4_Firmware</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
		<buildCommand>
			<name>org.eclipse.cdt.managedbuilder.core.genmakebuilder</name>
			<triggers>clean,full,incremental,</triggers>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.cdt.managedbuilder.core.ScannerConfigBuilder</name>
			<triggers>full,incremental,</triggers>
			<arguments>
			</arguments>
		</buildCommand>
	</buildSpec>
	<natures>
		<nature>org.eclipse.cdt.core.cnature</nature>
		<nature>org.eclipse.cdt.managedbuilder.core.managedBuildNature</nature>
		<nature>org.eclipse.cdt.managedbuilder.core.ScannerConfigNature</nature>
		<nature>fr.ac6.mcu.ide.core.MCUProjectNature</nature>
		<nature>fr.ac6.mcu.ide.core.MCUSingleCoreProjectNature</nature>
	</natures>
	<linkedResources>
		<link>
			<name>Common</name>
			<type>2</type>
			<locationURI>OSTC4/Common</locationURI>
		</link>
		<link>
			<name>Discovery</name>
			<type>2</type>
			<locationURI>OSTC4/Discovery</locationURI>
		</link>
	</linkedResources>
	<variableList>
		<variable>
			<name>OSTC4</name>
			<value>$%7BWORKSPACE_LOC%7D/ostc4</value>
		</variable>
	</variableList>
</projectDescription>