News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

The 27 July 2009 build (5716) is out.

Started by killerbot, July 27, 2009, 06:32:49 PM

Previous topic - Next topic

Jenna

Quote from: Biplab on July 28, 2009, 04:48:39 PM
Quote from: jens on July 28, 2009, 04:24:26 PM
Quote from: MortenMacFly on July 28, 2009, 03:18:40 PM
Quote from: jens on July 28, 2009, 02:09:35 PM
We parse the date with a regex, if we use automake on linux.
Linux I don't know. But he was talking about Windows. However - what's wrong with using the format as it is used in the (any) SVN repository? I mean: We *are* talking about a SVN revision here, right?

I know that he is talking about windows.

I don't know, why subversion uses this format for date/time of last commit (internally), but are there any objections against using a format, that's (better) human-readable for the date and time ?

The only cause would be, if we have to distinguish between to revision, that came in at the same second, but we also use the revision-number, so I don't see any problem.
And I don't think the patch to autorevision.cpp can break anything, unless the svn date-format changes.

Better consult with Thomas first. Once I wanted to fix this issue. But he didn't want to touch that code. I forgot the exact objection. :)

Thomas ?

Biplab

Quote from: jens on July 28, 2009, 05:18:38 PM
Quote from: Biplab on July 28, 2009, 04:48:39 PM
Quote from: jens on July 28, 2009, 04:24:26 PM
Quote from: MortenMacFly on July 28, 2009, 03:18:40 PM
Quote from: jens on July 28, 2009, 02:09:35 PM
We parse the date with a regex, if we use automake on linux.
Linux I don't know. But he was talking about Windows. However - what's wrong with using the format as it is used in the (any) SVN repository? I mean: We *are* talking about a SVN revision here, right?

I know that he is talking about windows.

I don't know, why subversion uses this format for date/time of last commit (internally), but are there any objections against using a format, that's (better) human-readable for the date and time ?

The only cause would be, if we have to distinguish between to revision, that came in at the same second, but we also use the revision-number, so I don't see any problem.
And I don't think the patch to autorevision.cpp can break anything, unless the svn date-format changes.

Better consult with Thomas first. Once I wanted to fix this issue. But he didn't want to touch that code. I forgot the exact objection. :)

Thomas ?

Yes!!
Be a part of the solution, not a part of the problem.

Jenna


MortenMacFly

Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

squalyl

dear codeblocks team I love you!

Just noticed some new features in this nightly: automatic } when I type a {. That's lovely. It saves a lot of time.

BUT: what did you do with the patch that saved me, about SDCC and static libs?

here: http://forums.next.codeblocks.org/index.php/topic,10741.msg73652.html#msg73652

I hoped it would be integrated in new nightlies  :cry:

(note : the change is fully OK, is there any reason not to integrate it in the main branch?)

crash report: http://www.mirari.fr/RUb0

MortenMacFly

Quote from: squalyl on July 28, 2009, 11:35:48 PM
BUT: what did you do with the patch that saved me, about SDCC and static libs?
...probably overseen? The next nightly will take care. I've submitted the modification.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

sbilsing

Hello CodeBlocks team,

First, CB is great. I use the nightly builds even for production. The degree of flexibility is just beyond everything I know from certain M$ products.
But the last 3 nightly builds include a bug in the command macro expansion. I filed a bug report here:
http://developer.berlios.de/bugs/?func=detailbug&bug_id=16072&group_id=5358

Regards
S.B.

vix

I did other tests, and I noticed that the encoding problem I described in my previous post
http://forums.next.codeblocks.org/index.php/topic,10912.msg74599.html#msg74599
appeared from the Nightly 5696.
Nightly Build 5678 works well.

Could be related to wxAui?

Loaden

Quote from: jens on July 28, 2009, 02:09:35 PM
Quote from: MortenMacFly on July 28, 2009, 12:53:55 PM
Quote from: Loaden on July 28, 2009, 10:32:15 AM
svn build rev 5717 (2009-07-28T07: 15:12.319835 Z) gcc 4.4.1 Windows / unicode
That's not wrong, that's exactly how SVN reports the date/time. It's just "a" format. Check any "entries" file in a .svn sub-foldr if you like. It's all the same.
We parse the date with a regex, if we use automake on linux.

We can do something similar on windows (of course without regexes).
Any objections against this patch:

Index: autorevision.cpp
===================================================================
--- autorevision.cpp (Revision 5716)
+++ autorevision.cpp (Arbeitskopie)
@@ -122,6 +122,8 @@
             if(d && d->GetText())
             {
                 date = d->GetText();
+                date.replace(date.find('T'),1," ");
+                date.resize(date.find('.'));
             }
             return 1;
         }

Thanks!
It's ok:
svn build rev 5722 (2009-07-30 09:59:52) gcc 4.4.1 Windows/unicode

killerbot

Quote from: sbilsing on July 30, 2009, 09:33:33 AM
Hello CodeBlocks team,

First, CB is great. I use the nightly builds even for production. The degree of flexibility is just beyond everything I know from certain M$ products.
But the last 3 nightly builds include a bug in the command macro expansion. I filed a bug report here:
http://developer.berlios.de/bugs/?func=detailbug&bug_id=16072&group_id=5358

Regards
S.B.


anyone already an idea on this regression ? wxAUi related ?

MortenMacFly

#25
Quote from: killerbot on July 30, 2009, 04:04:35 PM
anyone already an idea on this regression ? wxAUi related ?
If this is true:
QuoteApparently the bug was introduced in svn build 5678.
...then "no". Because the wxAUI merge came later.

EDIT: Cannot even reproduce. Works fine here...?!
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]


Jenna

Quote from: MortenMacFly on July 30, 2009, 04:31:16 PM
Quote from: killerbot on July 30, 2009, 04:04:35 PM
anyone already an idea on this regression ? wxAUi related ?
If this is true:
QuoteApparently the bug was introduced in svn build 5678.
...then "no". Because the wxAUI merge came later.

EDIT: Cannot even reproduce. Works fine here...?!

I can reproduce here (linux 64-bit).

I did not look into it deeper (no time), but I found a workaround (that might be a hint to find the bug):
double the $-sign and it works again (at least here).

Jenna

It's commit 5636, that leads to the error. I did not (yet) look for a solution.

killerbot

which is a change to 'compilercommandgenerator.cpp' base upon work of 'Biplab' : "replace macros for compiler options".
Basically 2 lines have been added, doing a macro substitution, could it be it is carried out too early ??