Re: [fpc-pascal] {$include %dateyear%}

2021-12-26 Thread James Richters via fpc-pascal
I can put some more thought into it.. but I'm wondering how to properly submit a change request for this documentation. James ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] {$include %dateyear%}

2021-12-25 Thread Ched via fpc-pascal
Well, Writeln('{$I %DATEMONTH%}'+'/'); can be compiled, but the answer is... {$I %DATEMONTH%} . I think that my level of english is by far too low to make the correct sentence. Cheers, James, Raoul Le 25.12.21 à 21:06, James Richters a écrit : I see what you mean... I thought it was an In

Re: [fpc-pascal] {$include %dateyear%}

2021-12-25 Thread James Richters via fpc-pascal
I see what you mean... I thought it was an Integer because If you do something like: Writeln({$I %DATEMONTH%}+'/'+{$I %DATEDAY%}+'/'+{$I %DATEYEAR%}); You get Error: Operator is not overloaded: "ShortInt" + "Char" But that's not what it is it's just like typing in hard coded numbers afte

Re: [fpc-pascal] {$include %dateyear%}

2021-12-25 Thread Ched via fpc-pascal
Helolo James, Thank you for your comment and proposal. As there is no type associated with non-string results, would it be better to say number instead of integer ? Or integer number ? Season's greetings ! Cheers, Ched' Le 24.12.2021 à 22:32, James Richters via fpc-pascal a écrit : I woul

Re: [fpc-pascal] {$include %dateyear%}

2021-12-24 Thread James Richters via fpc-pascal
I would agree that the documentation actually states quite clearly that they are ALL strings except %linenum% and the documentation should be improved to be accurate. Perhaps {$INCLUDE %XXX%} the {$INCLUDE} directive inserts a string or integer constant in the source code. Here XXX can be one