2013/10/4 Kurt Pattyn :
> In some markets like Avionics and Defense, it is simply forbidden for us to
> use exceptions.
> So, at least I think it should be possible to disable them in Qt if it was
> decided to allow them, otherwise we would be forced to use another
> framework.
There's no way we w
Builds are running again.
The same problem also occurred for QtDeclarative_stable, but that one is fixed
as well.
However, since we don't know the root cause for this problem we had, we can't
say it won't happen again. We'll keep our eyes open...
-Tony
From: Sarajärvi Tony
Sent: 3. lokakuuta
In some markets like Avionics and Defense, it is simply forbidden for us to use
exceptions.
So, at least I think it should be possible to disable them in Qt if it was
decided to allow them, otherwise we would be forced to use another framework.
Aside from that, and that is personal, I really like
On Fri, Oct 4, 2013 at 7:08 AM, Thiago Macieira
wrote:
> On quinta-feira, 3 de outubro de 2013 17:11:54, Alex Malyushytskyy wrote:
> > Assuming exceptions are enabled for signal/slots what is going to happen
> > with Qt::QueuedConnection?
> > As far as I understand at this point you can't catch e
On quinta-feira, 3 de outubro de 2013 17:11:54, Alex Malyushytskyy wrote:
> Assuming exceptions are enabled for signal/slots what is going to happen
> with Qt::QueuedConnection?
> As far as I understand at this point you can't catch exception in the
> signal.
If we choose to standardise that exce
Assuming exceptions are enabled for signal/slots what is going to happen
with Qt::QueuedConnection?
As far as I understand at this point you can't catch exception in the
signal.
That means you will have to do it in the event loop. What is going to
happen next? Re-throw it and an uncaught exception
Hi,
Intention is not to claim copyright to your document.
Please make a bug report on this and we'll take a look into if this needs to be
altered or not.
Yours,
Tuukka
Lähettäjä: development-bounces+tuukka.turunen=digia@qt-project.org
On quinta-feira, 3 de outubro de 2013 09:43:18, Marc Mutz wrote:
> Qt is a general-purpose framework library. As a library, its *only*
> purpose is to serve its users; as a framework, it mandates a certain
> structure on programs using it. As a general-purpose library, it can
> only assume very lit
On quinta-feira, 3 de outubro de 2013 10:36:44, Olivier Goffart wrote:
> > I dislike allowing this via the signal-slot mechanism because I see
> > throwing from a slot as incompatible with the connection semantics.
> >
> > That would mean any signal could throw ANY exception. It would also
> > pre
On Oct 3, 2013, at 4:09 AM, Sorvig Morten wrote:
> Do you happen to have xcb and/or pkgconfig installed via Macports? I can
> reproduce the build error in that case.
Ah, yep you're right -- I do.
> A quick workaround is to configure with "-no-pkg-config".
That did it.
> This should arguabl
I'm using QPrinter in Qt 4.8 to produce a PDF document. In the metadata of the
generated file (specifically the producer field) there is a Nokia copyright:
(C) 2011 Nokia Corporation and/or its subsidiary(-ies)
I traced this back to QPdfEnginePrivate::writeInfo(). Looking in Qt 5 I see the
On Oct 3, 2013, at 2:30 PM, Jørgen Lind wrote:
>>
>
> But if you happen to have pkg-config in your path, why should we then
> not use it. The user has "one way or the other" added it to the path,
> so why shouldn't it be used.
>
> I think the interesting question is why configure fails when yo
we have canceled all integrations, and reset all staging branches and
pending changes, so we hope everything is back to normal (for the time
being ...).
before you stage, rebase your changes and see whether they don't
disappear from the stack of pushable changes - some changes got
integrated witho
On 3 October 2013 11:09, Sorvig Morten wrote:
> On Oct 3, 2013, at 3:10 AM, Glen Mabey
> wrote:
>
>>
>> I'm on the dev branch but experienced this issue before the 5.2 and 5.3
>> branches split.
>>
>> macbookpro:qtbase$ ./configure -prefix ~/src/take2/install
>>
>>
>>
>> Running configuration
I can add to this that Google also disallows exceptions, as is stated in their
style guide:
http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml?showone=Exceptions#Exceptions
So, Qt is not alone in this regard.
On 03 Oct 2013, at 12:00, development-requ...@qt-project.org wrote:
> Fr
(sorry for jumping in the middle of the discussion)
>Quoting style guides that apply for applications can by definition not
>contain reasoning for library writers. Apps live in their own little
>dream world and can play with the compiler flags anyway they wish. They
>only target one App, after
We have a problem in Gerrit releated to QtBase_stable. We know what has gone
wrong, but we don't know how that's possible, nor how to fix it properly.
Needless to say, investigation is ongoing.
Thank you for your patience.
-Tony
Tony Sarajärvi
CI Tech Lead
Digia, Qt
___
Le 03/10/2013 10:36, Olivier Goffart a écrit :
> On Wednesday 02 October 2013 09:30:58 Thiago Macieira wrote:
>
>> That would mean any signal could throw ANY exception. It would also preempt
>> the execution of further slots, which might be important.
>>
>> Usually the person who connects a signal
On Oct 3, 2013, at 3:10 AM, Glen Mabey
wrote:
>
> I'm on the dev branch but experienced this issue before the 5.2 and 5.3
> branches split.
>
> macbookpro:qtbase$ ./configure -prefix ~/src/take2/install
>
>
>
> Running configuration tests...
> The test for linking against libxcb and suppor
On Wednesday 02 October 2013 09:30:58 Thiago Macieira wrote:
> On quarta-feira, 2 de outubro de 2013 07:13:11, Knoll Lars wrote:
> > +1. It's our decision not to use exceptions in Qt code, but I see quite a
> > bit of value in being able to throw exceptions from a slot if that's the
> > pattern a d
On 2013-10-02 20:39, André Pönitz wrote:
[...]
>
>
> tp://google-styleguide.googlecode.com/svn/trunk/cppguide.xml#Exceptions
> is for instance pretty concise: "We don't use C++ exceptions". They
> later
> give detailed reasoning and a conclusion including "Our advice against
> using exceptions
Hi All,
Is there any good documentation on the DNS resolver library (in Linux).
I've mostly been referring to manpages of resolver functions (res_init et
all) which gives an overview of the main functions.
However, I wanted to know more about the main "struct __res_state" used in
these functions.
22 matches
Mail list logo
