On Sat, Jun 9, 2012 at 10:25 AM, Andre Arpin wrote:
> I am having a hard time understanding the use of iterator in wxlua.
>
> I guess an iterator is created by wxString::const_iterator end() or
> wxString::const_iterator begin() for wxString which would be coded
> wx.wxString(str):end() but end is
>
> I agree that the current functions are awkward to use. I will make the
> input iterator argument optional.
>
I am having a hard time understanding the use of iterator in wxlua.
I guess an iterator is created by wxString::const_iterator end() or
wxString::const_iterator begin() for wxString
On Thu, Jun 7, 2012 at 10:09 AM, Andre Arpin wrote:
> using date:ParseDate(value, wx.wxString_const_iterator())
>
> seems to work but looking into the run time we see that the pointer to the
> iterator is a bad pointer not very desirable.
>
> supporting a single argument seems preferable.
I agree
using date:ParseDate(value, wx.wxString_const_iterator())
seems to work but looking into the run time we see that the pointer to the
iterator is a bad pointer not very desirable.
supporting a single argument seems preferable.
The following code works.
static int LUACALL wxLua_wxDateTime_ParseD
