Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
From: Igor Sapego <isapego@gridgain.com>
Date: Fri, 20 Jan 2017 20:24:46 +0300
Message-ID: <CALOGAozV6pf=ucLeMd7+bag6rfS4cGMixBYcrYDEZPA+C1R8_g@mail.gmail.com>
Subject: Abandon of the non-throwing version of C++ client API
To: dev@ignite.apache.org, user <user@ignite.apache.org>
Content-Type: multipart/alternative; boundary=001a1143fdb82287a0054689ed75
archived-at: Fri, 20 Jan 2017 17:24:59 -0000

--001a1143fdb82287a0054689ed75
Content-Type: text/plain; charset=UTF-8

Hi Igniters,

I'm the guy who mostly contribute in C++ Ignite client and I
need your advice. Mostly I'd like to hear from our users and
those who are experienced in C++. Currently we have two
versions of most API methods - the throwing one and the
one that returns error through output argument. This was initially
done because we were not sure which way of error-reporting
is going to be preferred by our users.

Now this approach bloats C++ API a lot and makes it harder to
maintain and optimize code. I propose like to abandon and deprecate
non-throwing version of API and only leave throwing version,
but first I want to hear from you guys - what do you think? Does
anyone use non-throwing version of the API? Maybe your toolchain
does not support exceptions or are you disabling them on purpose?

For those who prefer disabling exceptions I propose to introduce
some macros like IGNITE_DISABLE_EXCEPTIONS and add
some thread-local error-storing mechanism like ignite::GetLastError().

What do you guys think?

Best Regards,
Igor

--001a1143fdb82287a0054689ed75
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Igniters,</div><div><br></div><div>I&#39;m the guy=
 who mostly contribute in C++ Ignite client and I=C2=A0</div><div>need your=
 advice. Mostly I&#39;d like to hear from our users and=C2=A0</div><div>tho=
se who are experienced in C++. Currently we have two=C2=A0</div><div>versio=
ns of most API methods - the throwing one and the=C2=A0</div><div>one that =
returns error through output argument. This was initially</div><div>done be=
cause we were not sure which way of error-reporting=C2=A0</div><div>is goin=
g to be preferred by our users.</div><div><br></div><div>Now this approach =
bloats C++ API a lot and makes it harder to</div><div>maintain and optimize=
 code. I propose like to abandon and deprecate</div><div>non-throwing versi=
on of API and only leave throwing version,</div><div>but first I want to he=
ar from you guys - what do you think? Does</div><div>anyone use non-throwin=
g version of the API? Maybe your toolchain</div><div>does not support excep=
tions or are you disabling them on purpose?</div><div><br></div><div>For th=
ose who prefer disabling exceptions I propose to introduce<br></div><div>so=
me macros like IGNITE_DISABLE_EXCEPTIONS and add</div><div>some thread-loca=
l error-storing mechanism like ignite::GetLastError().</div><div><br></div>=
<div>What do you guys think?</div><br clear=3D"all"><div><div class=3D"gmai=
l_signature"><div dir=3D"ltr"><div>Best Regards,</div><div>Igor</div></div>=
</div></div>
</div>

--001a1143fdb82287a0054689ed75--