Ok, you are right, guys, there is no mention about this. But would it hurt
anybody to include such short patch to have this work, or only I think
that it would help ev++?
Anyway, I of course would like to use ev in object oriented way, so i use
dynamic loop. And with older releases, this
On Wed, Apr 20, 2011 at 03:58:40PM +0200, Richard Kojedzinszky
kri...@cflinux.hu wrote:
Ok, you are right, guys, there is no mention about this. But would
it hurt anybody to include such short patch to have this work, or
I think it would hurt people, yes.
only I think that it would help
Many thanks for your replay. The problem I have is that the code changed
that way that it does not compile at all. I think it is not a functional
change, but it does not work at all.
But if it is a pain for you to place that brackets, then skip them, i will
solve it. Or, to be consistent,
On Sun, Apr 17, 2011 at 09:25:26PM +0200, Richard Kojedzinszky
kri...@cflinux.hu wrote:
Dear Marc,
I dont see the relation between ev::dynamic_loop and the .once
function, as it is a function of loop_ref. Of course, I could write
ev::default_loop as well, as I've attached.
It doesn't
So for now, do you say that the whole c++ support is undocumented, and
unsupported?
Kojedzinszky Richard
On Mon, 18 Apr 2011, Marc Lehmann wrote:
On Sun, Apr 17, 2011 at 09:25:26PM +0200, Richard Kojedzinszky
kri...@cflinux.hu wrote:
Dear Marc,
I dont see the relation between
On Mon, Apr 18, 2011 at 3:16 PM, Richard Kojedzinszky kri...@cflinux.hu wrote:
So for now, do you say that the whole c++ support is undocumented, and
unsupported?
I think he means only the interfaces documented in the pod are
documented and supported at this time:
So for now, do you say that the whole c++ support is undocumented,
and unsupported?
Of course not - just the undocumented parts are unsupported. Undocumented
means not documented in the documentation. The documented parts are
supported.
--
The choice of a Deliantra, the