#
# INTRODUCTION:
#	Unified, simplified and nice solution for embedding of 
#	version-control-code-string into your code sources.
#	This is proposed just as GLUE to any
#	version-control-software of Your choice.
#
#
# MAIN ADVANTAGE:
#	no more hand typing of code line like this:
#		$VERSION = 1.01
#
#
# SYNOPSIS:
#	package MyTestPackage; use VERSION::RCS qw($Id: MyTestPackage.pm,v 1.3 2002/04/09 09:07:34 root Exp $);
#	print "Version of MyTestPackage is:", $VERSION, "\n";
#
#
# PROPOSAL:
#	( to all version-control-software developers )
#	help me to create modules compatible with your version control software.
#	Three single steps You should do:
#
#	-1- 
#	create properly named new module.
#	example: your version control softvare name is "VCSX", then you should create
#	module named VCSX.pm containing import() subroutine as described in following step...
#
#	-2-
#	edit the above sub import { ... } to be accepting the version control string
#	in your "VCSX" format. The string is passed via import() mechanism as
#	described in SYNOPSIS.
#
#	-3-
#	send me the module and I will do the rest. My e-mail is: Daniel.Peder@infoset.cz
#
#
# DETAILS:
# 	important fields ( of hash variable %VersionProperty ):
#
#	- format - 
#	is the name of this package (in our example VERSION::RCS), passed by 
#	import() mechanism. It is in fact format-style of used version string.
#
#	- number -
#	is the version number. It will be exported-and-assigned to
#	$VERSION variable in the proper namespace of calling package.
#
# 	other fields ( of hash variable %VersionProperty ):
#	
#	Intended just for possible future use.
#	Might be anything like garbage1, garbage2, garbage3, etc...
#	but it seems to be more meaningfull to give it some descriptive names
#
#
# NOTE:
#	I am not native english speaking. Don't hit my head for grammar.
#
#
# CONTACT:
#	Daniel.Peder@infoset.cz
#