[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    About KDE_NO_DEPRECATED
From:       JonAnder_Peņalba <jonan.debian () gmail ! com>
Date:       2011-06-23 15:44:45
Message-ID: BANLkTinQsztceqBkS_AwgMXFsG4yMSsZrQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi,

I've been doing some experiments with the KDE_NO_DEPRECATED define and I
have some doubts.

What is it exactly supposed to mean?
As I understand it, when compiling with this define, all deprecated code
should be ignored and the application should work as expected. So if an
application builds with KDE_NO_DEPRECATED, you can be sure it's not using
any deprecated code that might be removed in future versions.
This is not the result I get. When I compile with this define, I get strange
results that vary from weird behavior to segfaults.

Am I using this define in a wrong way?

[Attachment #5 (text/html)]

Hi,<br><br>I&#39;ve been doing some experiments with the KDE_NO_DEPRECATED define and \
I have some <span id="result_box" class="short_text" lang="en"><span title="Click for \
alternate translations" class="hps">doubts</span></span>.<br> <br>What is it exactly \
supposed to mean?<br>As I understand it, when compiling with this define, all \
deprecated code should be ignored and the application should work as expected. So if \
an application builds with KDE_NO_DEPRECATED, you can be sure it&#39;s not using any \
deprecated code that might be removed in future versions.<br> This is not the result \
I get. When I compile with this define, I get strange results that vary from weird \
behavior to segfaults.<br><br>Am I using this define in a wrong way?<br><span \
id="result_box" class="short_text" lang="en"><span title="Click for alternate \
translations" class="hps"></span></span>



>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]