Re: EV_SET() better C++ compat with alternative implementations

2019-08-25 Thread Kamil Rytarowski
On 25.08.2019 18:10, Joerg Sonnenberger wrote: > On Sun, Aug 25, 2019 at 04:59:41PM +0100, Roy Marples wrote: >> On 25/08/2019 16:48, Joerg Sonnenberger wrote: >>> On Sun, Aug 25, 2019 at 04:43:51PM +0100, Roy Marples wrote: On 25/08/2019 15:39, Joerg Sonnenberger wrote: > There is no tech

Re: EV_SET() better C++ compat with alternative implementations

2019-08-25 Thread Joerg Sonnenberger
On Sun, Aug 25, 2019 at 04:59:41PM +0100, Roy Marples wrote: > On 25/08/2019 16:48, Joerg Sonnenberger wrote: > > On Sun, Aug 25, 2019 at 04:43:51PM +0100, Roy Marples wrote: > > > On 25/08/2019 15:39, Joerg Sonnenberger wrote: > > > > There is no technical reason really for prefering void * > > >

Re: EV_SET() better C++ compat with alternative implementations

2019-08-25 Thread Roy Marples
On 25/08/2019 16:48, Joerg Sonnenberger wrote: On Sun, Aug 25, 2019 at 04:43:51PM +0100, Roy Marples wrote: On 25/08/2019 15:39, Joerg Sonnenberger wrote: There is no technical reason really for prefering void * Having to write code to exclusively deal with NetBSD's different API to compile wi

Re: EV_SET() better C++ compat with alternative implementations

2019-08-25 Thread Joerg Sonnenberger
On Sun, Aug 25, 2019 at 04:43:51PM +0100, Roy Marples wrote: > On 25/08/2019 15:39, Joerg Sonnenberger wrote: > > There is no technical reason really for prefering void * > Having to write code to exclusively deal with NetBSD's different API to > compile without warnings sounds like a pretty good t

Re: EV_SET() better C++ compat with alternative implementations

2019-08-25 Thread Kamil Rytarowski
On 25.08.2019 17:38, Joerg Sonnenberger wrote: > On Sun, Aug 25, 2019 at 05:12:26PM +0200, Kamil Rytarowski wrote: >> I want to see the original state of void* so all casts will be unneded. > > But it doesn't. Casts are *still* necesseary when using integer indices > as data. > It's obvious in t

Re: EV_SET() better C++ compat with alternative implementations

2019-08-25 Thread Roy Marples
On 25/08/2019 15:39, Joerg Sonnenberger wrote: There is no technical reason really for prefering void * Having to write code to exclusively deal with NetBSD's different API to compile without warnings sounds like a pretty good technical reason to me. And I'm just talking about the C interface.

Re: EV_SET() better C++ compat with alternative implementations

2019-08-25 Thread Joerg Sonnenberger
On Sun, Aug 25, 2019 at 05:12:26PM +0200, Kamil Rytarowski wrote: > I want to see the original state of void* so all casts will be unneded. But it doesn't. Casts are *still* necesseary when using integer indices as data. > Since B lang times we used pointers and integers as the same data type. >

Re: EV_SET() better C++ compat with alternative implementations

2019-08-25 Thread Kamil Rytarowski
On 25.08.2019 16:39, Joerg Sonnenberger wrote: > On Sun, Aug 18, 2019 at 08:58:15PM -, Valery Ushakov wrote: >> Joerg Sonnenberger wrote: >> >>> On Sun, Aug 18, 2019 at 05:05:33PM +0200, Kamil Rytarowski wrote: Ping? Can we switch from intptr_t to void*? >>> >>> Can we just go back to the

Re: EV_SET() better C++ compat with alternative implementations

2019-08-25 Thread Joerg Sonnenberger
On Sun, Aug 18, 2019 at 08:58:15PM -, Valery Ushakov wrote: > Joerg Sonnenberger wrote: > > > On Sun, Aug 18, 2019 at 05:05:33PM +0200, Kamil Rytarowski wrote: > >> Ping? Can we switch from intptr_t to void*? > > > > Can we just go back to the original state? > > Anything wrong with the tem

Re: EV_SET() better C++ compat with alternative implementations

2019-08-25 Thread maya
On Mon, Aug 19, 2019 at 09:58:32AM +0200, Jaromir Dolecek wrote: > Please wait with any possible type switch couple more days, I’ll be back from > vacations on Wednesday and I will check this by then. > ping