On 31.01.19 19:33, Tanu Kaskinen wrote:
On Mon, 2019-01-28 at 18:43 +0100, Georg Chini wrote:
On 28.01.19 18:37, Georg Chini wrote:
On 28.01.19 18:05, Tanu Kaskinen wrote:
On Mon, 2019-01-28 at 17:50 +0100, Georg Chini wrote:
2) For read_string() and read_raw() it is difficult to retain a
On Mon, 2019-01-28 at 18:43 +0100, Georg Chini wrote:
> On 28.01.19 18:37, Georg Chini wrote:
> > On 28.01.19 18:05, Tanu Kaskinen wrote:
> > > On Mon, 2019-01-28 at 17:50 +0100, Georg Chini wrote:
> > > > > > 2) For read_string() and read_raw() it is difficult to retain a
> > > > > > default
> >
On 28.01.19 18:37, Georg Chini wrote:
On 28.01.19 18:05, Tanu Kaskinen wrote:
On Mon, 2019-01-28 at 17:50 +0100, Georg Chini wrote:
2) For read_string() and read_raw() it is difficult to retain a
default
value.
The string returned by the functions is a char, but it must not be
freed
because
On 28.01.19 18:05, Tanu Kaskinen wrote:
On Mon, 2019-01-28 at 17:50 +0100, Georg Chini wrote:
2) For read_string() and read_raw() it is difficult to retain a default
value.
The string returned by the functions is a char, but it must not be freed
because it is part of the larger parameter
On Mon, 2019-01-28 at 17:50 +0100, Georg Chini wrote:
> > > 2) For read_string() and read_raw() it is difficult to retain a default
> > > value.
> > > The string returned by the functions is a char, but it must not be freed
> > > because it is part of the larger parameter string. So the string
On 28.01.19 16:48, Tanu Kaskinen wrote:
On Sat, 2019-01-26 at 23:15 +0100, Georg Chini wrote:
Hi Tanu,
as already said in a previous mail, I am working again on the messaging API.
I hope you remember enough of your review that you can answer a couple
of questions:
1) I seem to remember that
