On terça-feira, 28 de janeiro de 2014 10:59:08, Oswald Buddenhagen wrote:
On Mon, Jan 27, 2014 at 07:25:34AM -0800, Thiago Macieira wrote:
On segunda-feira, 27 de janeiro de 2014 11:25:17, Konrad Rosenbaum wrote:
Neither do I, but as a user of Qt I've inadvertently tricked myself
often
On Mon, Jan 27, 2014 at 07:25:34AM -0800, Thiago Macieira wrote:
On segunda-feira, 27 de janeiro de 2014 11:25:17, Konrad Rosenbaum wrote:
Neither do I, but as a user of Qt I've inadvertently tricked myself often
enough with additional trailing spaces (please highlight those as well!),
On 27/01/14 00:03, Thiago Macieira thiago.macie...@intel.com wrote:
On domingo, 26 de janeiro de 2014 20:17:20, Knoll Lars wrote:
I usually prefer the output in utf8, as it gives readable strings (at
least on Mac and Linux as long as you don¹t mess with the locale).
Escaped
strings are much
On segunda-feira, 27 de janeiro de 2014 08:06:58, Knoll Lars wrote:
With my change as it is, you'd see:
Actual (s1): Thiago Jos\u00E9 Macieira / Lars Knoll
Expected (s2): Thiago Jose\u0301 Macieira \u2215 L\u0430rs Knoll
I know that, but we’re usually not writing our auto tests to try and
On Monday, Monday 27 January 2014 at 09:06, Knoll Lars wrote:
With my change as it is, you'd see:
Actual (s1): Thiago Jos\u00E9 Macieira / Lars Knoll
Expected (s2): Thiago Jose\u0301 Macieira \u2215 L\u0430rs Knoll
I know that, but we’re usually not writing our auto tests to try and
trick
On Tuesday, 21 January 2014 01:05:07 CEST, Thiago Macieira wrote:
Actual (s) : \u221212\u20A0\uD800\uDC00
Expected (s2): \u221212\u20AC\uD800\uDC00
[...]
- all backslashes as \\
- the following characters as their escape sequences: \r, \n, \t, \b, \f
- all other control characters
On 21 Jan 2014, at 01:05, Thiago Macieira thiago.macie...@intel.com wrote:
I was writing a test today and QtTest told me:
Actual (s) : ?12???
Expected (s2): ?12???
So I went, duh, ok, it looks the same to me but what's behind those question
marks.
After a bit of changes
On domingo, 26 de janeiro de 2014 12:36:27, Jan Kundrát wrote:
On Tuesday, 21 January 2014 01:05:07 CEST, Thiago Macieira wrote:
Actual (s) : \u221212\u20A0\uD800\uDC00
Expected (s2): \u221212\u20AC\uD800\uDC00
[...]
- all backslashes as \\
- the following characters as
On 26/01/14 20:39, Thiago Macieira thiago.macie...@intel.com wrote:
On domingo, 26 de janeiro de 2014 12:36:27, Jan Kundrát wrote:
On Tuesday, 21 January 2014 01:05:07 CEST, Thiago Macieira wrote:
Actual (s) : \u221212\u20A0\uD800\uDC00
Expected (s2): \u221212\u20AC\uD800\uDC00
On domingo, 26 de janeiro de 2014 20:17:20, Knoll Lars wrote:
I usually prefer the output in utf8, as it gives readable strings (at
least on Mac and Linux as long as you don¹t mess with the locale). Escaped
strings are much more tedious to debug for me in most cases. So I¹d like
to ask for at
On Mon, Jan 20, 2014 at 7:05 PM, Thiago Macieira
thiago.macie...@intel.comwrote:
I was writing a test today and QtTest told me:
Actual (s) : ?12???
Expected (s2): ?12???
So I went, duh, ok, it looks the same to me but what's behind those
question
marks.
After a bit of changes
On terça-feira, 21 de janeiro de 2014 13:31:40, Matt Broadstone wrote:
I think this would be great as well, but also if there was maybe an io
manipulator to print the hex if you want to look at that as well. Ideally
such a manipulator would print the whole hex, currently the hex printed for
I was writing a test today and QtTest told me:
Actual (s) : ?12???
Expected (s2): ?12???
So I went, duh, ok, it looks the same to me but what's behind those question
marks.
After a bit of changes [https://codereview.qt-project.org/76100], it now
prints:
Actual (s) :
13 matches
Mail list logo
