fP environment variables oddity

[Jean-Pierre A. Radley]

Being the sloppy typist that I am, I managed to mess up fP's config file
so that it contained:

	wwnodf=on
	JPVER=ON
	lfCMARK=80

The effect was that filePro behaved exactly as it would if those entries
were set to:

	PFNODF=on
	PFVER=ON
	PFCMARK=80
or
	FPNODF=on
	FPVER=ON
	FPCMARK=80

I've only spent three minutes testing this phenomenon, but so far I've
found that ANY two characters could do -- why, even
	#\ver=yes
will cause an fP binary to display its version!

-- 
JP