Mattias Gaertner wrote:
http://wiki.lazarus.freepascal.org/Lazarus/FPC_Libraries
When the ToDos are solved the IDE can be extended.
"ToDo: proposal how the IDE should create version numbers"
I'm just giving my comments here... maybe my knowledge on these subjects
is old... if it is... then I accept that....
I can see what the documentation is getting at....
- be able to keep version #s
- be able to generate them in the IDE
- be able to read them at runtime (to check version #)
- make something that is reasonably cross platform
Under windows, version #s of dll's are usually kept in the dll header.
Under unix, it is embedded in the filename.
Not sure how to reconcile the two....
but...
if we are building a library (class).... it might be possible to
autogenerate a property within the class for the version... and have
this carried down....
class mypdfwriter : TObject
private
fversion : float = 1.1;
published
property version : float read fversion;
end;
that probably would only work if there was one class per source file.....
but the idea would be to carry the version property into the dll header
or .so filename.
maybe another option could be to change the "interface" keyword.....
eg..
interface version 1.8 {defining our module to be version 1.8}
uses Sockets > 1.4, OpenGL 2.3 {needs Sockets > 1.4, OpenGL must be 2.3}
etc......
that would be a very simple to use extension..... for the programmer....
also easy for the IDE to read and modify....
not sure how difficult to do at the backend..... compiler etc
Regards
David
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
