On 11/5/2012 21:31, Ruben Van Boxem wrote:
2012/11/5 JonY jo...@users.sourceforge.net
On 11/5/2012 21:16, Ruben Van Boxem wrote:
2012/11/5 JonY jo...@users.sourceforge.net
On 11/5/2012 20:44, Ozkan Sezer wrote:
If older gcc (I guess 4.6 is common as the old gcc) is OK with it, then
somehow I think pointers are the way to go when modifying an iterator function
argument. but I am having problems. I have a pointer to an iterator.
gcc wants me to dereference a *third* time. it says to use - and I know a-b
is the same as *a.b
but gcc doesn't see it this way I guess. or
I'm hoping my load fail (and the OP's) turns out to be the issue of
modules linking against two different CRT versions. PeStudio tells me
my msvcrt.dll linked .pyd's try to use _errno, __dllonexit, fflush,
free, malloc, and strcmp from msvcr90.dll.
Just for the heck of it, I changed
that would be nice...
From: Yves yves.per...@modusfx.com
To: mingw-w64-public@lists.sourceforge.net
mingw-w64-public@lists.sourceforge.net
Sent: Monday, November 5, 2012 10:49 AM
Subject: Re: [Mingw-w64-public] MinWG64 on Windows, for Windows?
Hi Ruben,
Op 6 nov. 2012 11:04 schreef Jim Michaels jmich...@yahoo.com het
volgende:
somehow I think pointers are the way to go when modifying an iterator
function argument. but I am having problems. I have a pointer to an
iterator.
An iterator is the generalization of pointers for non-sequential
I'm hoping my load fail (and the OP's) turns out to be the issue of
modules linking against two different CRT versions. PeStudio tells me
my msvcrt.dll linked .pyd's try to use _errno, __dllonexit, fflush,
free, malloc, and strcmp from msvcr90.dll.
Just for the heck of it, I changed
On 11/6/2012 16:57, JonY wrote:
Actually, according to
http://msdn.microsoft.com/en-us/library/28d5ce15%28v=vs.80%29.aspx
In Visual C++ 2005, vswprintf conforms to the ISO C Standard, which
requires the second parameter, count, of type size_t. To force the old
nonstandard behavior, define
With this in mind, which package should I use to compile on Windows
for Linux?
You probably see it coming… which package should I use to compile on
Windows for MacOSX?
In another words, what solution is there to cross compile on
Windows, for Windows, Linux and
On Tue, Nov 6, 2012 at 6:50 AM, Zouzou wrote:
With this in mind, which package should I use to compile on Windows
for Linux?
You probably see it coming… which package should I use to compile on
Windows for MacOSX?
In another words, what solution is there to cross compile
On Tue, Nov 6, 2012 at 5:04 AM, Václav Šmilauer e...@doxos.eu wrote:
I'm hoping my load fail (and the OP's) turns out to be the issue of
modules linking against two different CRT versions. PeStudio tells me
my msvcrt.dll linked .pyd's try to use _errno, __dllonexit, fflush,
free, malloc, and
Hi Jim!
A gentle suggestion ...
On Tue, Nov 6, 2012 at 5:03 AM, Jim Michaels jmich...@yahoo.com wrote:
somehow I think pointers are the way to go when modifying an iterator
function argument. but I am having problems. I have a pointer to an
iterator.
...
Many (by no means all) of your
On Tue, Nov 6, 2012 at 8:55 AM, K. Frank wrote:
Hi Jim!
A gentle suggestion ...
Oh, don't be too gentle. ;D
On Tue, Nov 6, 2012 at 5:03 AM, Jim Michaels wrote:
somehow I think pointers are the way to go when modifying an iterator
function argument. but I am having problems. I have a
2012/11/6 Earnie Boyd ear...@users.sourceforge.net
On Tue, Nov 6, 2012 at 8:55 AM, K. Frank wrote:
Hi Jim!
A gentle suggestion ...
Oh, don't be too gentle. ;D
On Tue, Nov 6, 2012 at 5:03 AM, Jim Michaels wrote:
somehow I think pointers are the way to go when modifying an iterator
13 matches
Mail list logo
