> Thanks for the comments Ian. To help determine whether or not this RFE
> should be included, I have updated the patch to apply to a clean checkout
> of branches/branch-1.3 rev 6985.
Thanks - been playing about with this patch applied to a clean checkout, and as
you indicated, it does not fix
> [..]it seems [the Microsoft] _snprintf() doesn't follow the C99 spec,
> so the function apparently works incorrectly [or at least unexpectedly
> if you're used to the C99 spec version) on the very
> boundary conditions it's supposed to protect us from. eg:
The following is a p
Ian MacArthur wrote:
>
>> Thanks for the comments Ian. To help determine whether or not this RFE
>> should be included, I have updated the patch to apply to a clean checkout
>> of branches/branch-1.3 rev 6985.
>
>
> Thanks - been playing about with this patch applied to a clean checkout,
> and
On 30 Dec 2009, at 19:38, Alvin wrote:
>
> It could "Just Work" but you might need to first call xtype() in
> Fl_Menu or
> Fl_Menu_ (I forget where the ctor for Fl_Menu is defined) for it to
> work.
OK - I'll try playing around a bit more. Didn't get a chance today,
my wee boy has a nasty c
On 30 Dec 2009, at 19:24, Greg Ercolano wrote:
> Solution on win32 is to change _snprintf() to _snprintf_s()
> with the _TRUNCATE macro as the third argument. But there's no
> clear way to use a macro shortcut to do this (since this is a
> varargs function), so a cross pl
imacarthur wrote:
> On 30 Dec 2009, at 19:24, Greg Ercolano wrote:
>> Solution on win32 is to change _snprintf() to _snprintf_s()
>> with the _TRUNCATE macro as the third argument. But there's no
>> clear way to use a macro shortcut to do this (since this is a
>> varargs functio
imacarthur wrote:
> On 30 Dec 2009, at 19:24, Greg Ercolano wrote:
>> Solution on win32 is to change _snprintf() to _snprintf_s()
>> with the _TRUNCATE macro as the third argument. But there's no
>> clear way to use a macro shortcut to do this (since this is a
>> varargs functio
