In Harbour we have, __DATE__ which returns the date when the code was compiled.
Below is the text from its help file,
Now, can we have similar in B4A ? i.e. __DATE__ for apk compile time date.
[SOLVED] See Don's reply and also Erel's reply in it.
Regards,
Anand
Below is the text from its help file,
Harbour automatically defines some macros, recognized by preprocessor (they're kind of inbuild #defines), which, if present in source-code, are evaluated (during preprocessing) and be substituted by specific internal information about code being processed, e.g. filename and line, the compilation date/time, as well as, harbour version, environment platform, architecture, endianness and such. These inbuild #defines can be referenced inside user code using their literal identifiers; some of the most common of them are:
__DATE__ , __TIME__
the build date and time, that is, the date/time when the particular .prg file was compiled, in the form: YYYYMMDD , HH:MM:SS respectively.
__DATE__ , __TIME__
the build date and time, that is, the date/time when the particular .prg file was compiled, in the form: YYYYMMDD , HH:MM:SS respectively.
Now, can we have similar in B4A ? i.e. __DATE__ for apk compile time date.
[SOLVED] See Don's reply and also Erel's reply in it.
Regards,
Anand
Last edited:
