On Wed, May 25, 2016, Tom Hacohen wrote:
> On 25/05/16 12:01, Daniel Kolesa wrote:
> > Hello,
> >
> > I've started removal of support for pointers in Eolian in order to
> > bring the language one level up and make it easier to do bindings.
> > This has already been done for class handles and for co
On Wed, 25 May 2016 12:01:59 +0100 Daniel Kolesa
wrote:
> Hello,
>
> I've started removal of support for pointers in Eolian in order to
> bring the language one level up and make it easier to do bindings.
> This has already been done for class handles and for complex types
> like array, hash, it
On 25/05/16 14:40, Daniel Kolesa wrote:
> On Wed, May 25, 2016 at 2:37 PM, Felipe Magno de Almeida
> wrote:
>> On Wed, May 25, 2016 at 9:38 AM, Daniel Kolesa wrote:
>>> On Wed, May 25, 2016 at 1:34 PM, Tom Hacohen wrote:
>>
>> [snip]
>>
Thank you for the attempted correction, but I mean inc
On Wed, May 25, 2016 at 2:37 PM, Felipe Magno de Almeida
wrote:
> On Wed, May 25, 2016 at 9:38 AM, Daniel Kolesa wrote:
>> On Wed, May 25, 2016 at 1:34 PM, Tom Hacohen wrote:
>
> [snip]
>
>>> Thank you for the attempted correction, but I mean increased burden,
>>> because that's yet another type
On Wed, May 25, 2016 at 9:38 AM, Daniel Kolesa wrote:
> On Wed, May 25, 2016 at 1:34 PM, Tom Hacohen wrote:
[snip]
>> Thank you for the attempted correction, but I mean increased burden,
>> because that's yet another type they need to take care of.
>
> They need to take care of it either way, j
On Wed, May 25, 2016 at 1:34 PM, Tom Hacohen wrote:
> On 25/05/16 13:11, Daniel Kolesa wrote:
>> On Wed, May 25, 2016 at 12:53 PM, Tom Hacohen wrote:
>>> On 25/05/16 12:01, Daniel Kolesa wrote:
Hello,
I've started removal of support for pointers in Eolian in order to
bring the
On 25/05/16 13:11, Daniel Kolesa wrote:
> On Wed, May 25, 2016 at 12:53 PM, Tom Hacohen wrote:
>> On 25/05/16 12:01, Daniel Kolesa wrote:
>>> Hello,
>>>
>>> I've started removal of support for pointers in Eolian in order to
>>> bring the language one level up and make it easier to do bindings.
>>>
On Wed, May 25, 2016 at 12:53 PM, Tom Hacohen wrote:
> On 25/05/16 12:01, Daniel Kolesa wrote:
>> Hello,
>>
>> I've started removal of support for pointers in Eolian in order to
>> bring the language one level up and make it easier to do bindings.
>> This has already been done for class handles an
On 25/05/16 12:01, Daniel Kolesa wrote:
> Hello,
>
> I've started removal of support for pointers in Eolian in order to
> bring the language one level up and make it easier to do bindings.
> This has already been done for class handles and for complex types
> like array, hash, iterator etc. but cur
On 25 May 2016 at 20:48, Daniel Kolesa wrote:
> On Wed, May 25, 2016 at 12:29 PM, Jean-Philippe André
> wrote:
> > Hi q66,
> >
> > It would be good to keep pointer support for void*. These APIs would be
> > limited to C (and maybe C++) only.
> > I have the evas image native surface in mind, as w
On Wed, May 25, 2016 at 12:29 PM, Jean-Philippe André wrote:
> Hi q66,
>
> It would be good to keep pointer support for void*. These APIs would be
> limited to C (and maybe C++) only.
> I have the evas image native surface in mind, as well as the gfx buffer
> map/unmap.
>
> Again, this is only for
Hi q66,
It would be good to keep pointer support for void*. These APIs would be
limited to C (and maybe C++) only.
I have the evas image native surface in mind, as well as the gfx buffer
map/unmap.
Again, this is only for C/C++. Maybe a @native tag could come along?
If that's not possible, we nee
Hello,
I've started removal of support for pointers in Eolian in order to
bring the language one level up and make it easier to do bindings.
This has already been done for class handles and for complex types
like array, hash, iterator etc. but currently one big obstacle in the
way is strings. I ha
13 matches
Mail list logo
