Hi,
I'm using fpc 2.6.4.
While i was playing a bit with issue
http://bugs.freepascal.org/view.php?id=20522 I stmbled upon unexpected
behaviour of StrToDate function.
StrToDate('6-12-2011 ') (note the space at the end) actually gives me 6-12-2014.
===
program stodate;
On 10/05/2014 13:55, Bart wrote:
Hi,
I'm using fpc 2.6.4.
While i was playing a bit with issue
http://bugs.freepascal.org/view.php?id=20522 I stmbled upon unexpected
behaviour of StrToDate function.
StrToDate('6-12-2011 ') (note the space at the end) actually gives me 6-12-2014.
...
Could
On Sat, 10 May 2014, Bart wrote:
Hi,
I'm using fpc 2.6.4.
While i was playing a bit with issue
http://bugs.freepascal.org/view.php?id=20522 I stmbled upon unexpected
behaviour of StrToDate function.
StrToDate('6-12-2011 ') (note the space at the end) actually gives me 6-12-2014.
That is
On 5/10/14, Michael Van Canneyt mich...@freepascal.org wrote:
StrToDate('6-12-2011 ') (note the space at the end) actually gives me
6-12-2014.
That is because the last part is not 'correct' (contains trailing garbage)
and
then the strtodate assumes the year is missing, and substitutes the
On Sat, 10 May 2014, Bart wrote:
On 5/10/14, Michael Van Canneyt mich...@freepascal.org wrote:
StrToDate('6-12-2011 ') (note the space at the end) actually gives me
6-12-2014.
That is because the last part is not 'correct' (contains trailing garbage)
and
then the strtodate assumes the
On 5/10/14, Michael Van Canneyt mich...@freepascal.org wrote:
Fixed.
You fixed it faste then it took me to type the bugreport!
I cannot test with trunk, so feel free to close the issue in the bugtracker.
B.t.w. I could not find an entry in Product version for 2.6.4 (or
2.7.1 for that matter).
On Sat, 10 May 2014, Bart wrote:
On 5/10/14, Michael Van Canneyt mich...@freepascal.org wrote:
Fixed.
You fixed it faste then it took me to type the bugreport!
I cannot test with trunk, so feel free to close the issue in the bugtracker.
Will do, thanks.
B.t.w. I could not find an
On 10.05.2014 16:20, Michael Van Canneyt wrote:
B.t.w. I could not find an entry in Product version for 2.6.4 (or
2.7.1 for that matter).
Where should I report this?
You should not. There is a version 2.6.4, I added a version 'trunk'.
To avoid having to re-create each trunk version.
I
On Sat, 10 May 2014, Sven Barth wrote:
On 10.05.2014 16:20, Michael Van Canneyt wrote:
B.t.w. I could not find an entry in Product version for 2.6.4 (or
2.7.1 for that matter).
Where should I report this?
You should not. There is a version 2.6.4, I added a version 'trunk'.
To avoid having
On 10/05/14 16:20, Michael Van Canneyt wrote:
You should not. There is a version 2.6.4, I added a version 'trunk'.
To avoid having to re-create each trunk version.
I don't think that is good. It will make it much harder to determine
which trunk version the bug report is about. It makes it
On 10/05/14 17:37, Michael Van Canneyt wrote:
On Sat, 10 May 2014, Sven Barth wrote:
On 10.05.2014 16:20, Michael Van Canneyt wrote:
I believe it was intentional that we didn't have a trunk version. At
least that's what I rememeber...
Yes, in hindsight a bad idea. I removed it meanwhile.
i'm using git to pull a project from sourceforge to a windows box and to a linux
box... on windows, the project compiles fine... on linux, though, all of the
files' names are lowercase but the sources have upper and CaMeL cased file names
in the uses and include statements... i have no
On Sat, 10 May 2014, waldo kitty wrote:
i'm using git to pull a project from sourceforge to a windows box and to a
linux box... on windows, the project compiles fine... on linux, though, all
of the files' names are lowercase but the sources have upper and CaMeL cased
file names in the
On 10.05.2014 20:09, waldo kitty wrote:
i'm using git to pull a project from sourceforge to a windows box and to
a linux box... on windows, the project compiles fine... on linux,
though, all of the files' names are lowercase but the sources have upper
and CaMeL cased file names in the uses and
On 5/10/2014 2:18 PM, Michael Van Canneyt wrote:
On Sat, 10 May 2014, waldo kitty wrote:
i surely don't want to have to edit the sources to lowercase all the uses and
includes statements every time i update my local repositories... how can i get
it to compile on linux no matter what case the
On 5/10/2014 5:14 PM, Sven Barth wrote:
On 10.05.2014 20:09, waldo kitty wrote:
i'm using git to pull a project from sourceforge to a windows box and to
a linux box... on windows, the project compiles fine... on linux,
though, all of the files' names are lowercase but the sources have upper
16 matches
Mail list logo
