Re: [E-devel] Eo: static methods or C syntax sugar for class methods?

>> but if we do a macro that counts the number of parameters and if no >> class is given it would assume the default class (base), that's easier >> to use. >> > > I'm a bit worried about the naming scheme for those macros, as they would > then have to merge a full method name (eg.

Re: [E-devel] Eo: static methods or C syntax sugar for class methods?

Hey k-s, On 20 December 2016 at 20:03, Gustavo Sverzut Barbieri wrote: > On Mon, Dec 19, 2016 at 11:05 PM, Jean-Philippe André > wrote: > > On 19 December 2016 at 21:10, Gustavo Sverzut Barbieri < > barbi...@gmail.com> > > While these are nice to be

Re: [E-devel] Eo: static methods or C syntax sugar for class methods?

On 20/12/16 11:03, Gustavo Sverzut Barbieri wrote: > On Mon, Dec 19, 2016 at 11:05 PM, Jean-Philippe André > wrote: >> Hi, >> >> On 19 December 2016 at 21:10, Gustavo Sverzut Barbieri >> wrote: >> >>> Hi all, >>> >>> In Efl.Net I've created couple of

Re: [E-devel] Eo: static methods or C syntax sugar for class methods?

On Mon, Dec 19, 2016 at 11:05 PM, Jean-Philippe André wrote: > Hi, > > On 19 December 2016 at 21:10, Gustavo Sverzut Barbieri > wrote: > >> Hi all, >> >> In Efl.Net I've created couple of "constructors" functions to help the >> user with common tasks, such

Re: [E-devel] Eo: static methods or C syntax sugar for class methods?

Hi, On 19 December 2016 at 21:10, Gustavo Sverzut Barbieri wrote: > Hi all, > > In Efl.Net I've created couple of "constructors" functions to help the > user with common tasks, such as: > Hmm. Sorry to be pedantic, but you've created @class functions, not constructor

[E-devel] Eo: static methods or C syntax sugar for class methods?

Hi all, In Efl.Net I've created couple of "constructors" functions to help the user with common tasks, such as: src/lib/ecore_con/efl_net_ip_address.eo: - create(port, address) - create_sockaddr(sockaddr) - parse(string) - resolve(string, family, flags) (returns