On 17.10.12 14:05, Gustaf Neumann wrote:
>> #ifdef NS_NOCOMPAT
>> -# error "No compatibility macros at present"
>> +// # error "No compatibility macros at present"
>> #endif
>>
>> This is my error, sorry, should be under _WIN64
>>
>> ...
> Is anybody aware about NS_NOCOMPAT ?
> This seem
%" "I64d" " %" "I64d"
is equivalent with
"%d %d %d %I64d %I64d %I64d %I64d"
-gn
>
> -Original Message-----
> From: Gustaf Neumann [mailto:neum...@wu.ac.at]
> Sent: 17 October 2012 14:06
> To: naviserver-devel@lists.sourceforge.net
%" "I64d" " %" "I64d"
is equivalent with
"%d %d %d %I64d %I64d %I64d %I64d"
-gn
>
> -Original Message-----
> From: Gustaf Neumann [mailto:neum...@wu.ac.at]
> Sent: 17 October 2012 14:06
> To: naviserver-devel@lists.sourceforge.net
>
Is this maybe version dependent? to be on the safe side, i
added PRIu64 in case it is not defined
-g
On 17.10.12 14:25, Ibrahim Tannir wrote:
> Hi Gustaf,
>
> Quickly grepped all include files. No PRI* defined anywhere.
> Maurizio must have missed this one.
>
> Cheers,
> Ibrahim
>
> On 17-Oct-12 1
er 2012 14:06
To: naviserver-devel@lists.sourceforge.net
Subject: Re: [naviserver-devel] [AOLSERVER] Naviserver Win-64 Sources
On 17.10.12 12:35, Maurizio Martignano wrote:
>
> +#ifdef _WIN64
> +Ns_DStringPrintf(dsPtr, "%d %d %d %l64d %l64d %l64d
> %l64d",
> +#el
Hi Gustaf,
Quickly grepped all include files. No PRI* defined anywhere.
Maurizio must have missed this one.
Cheers,
Ibrahim
On 17-Oct-12 14:05, Gustaf Neumann wrote:
> On 17.10.12 12:35, Maurizio Martignano wrote:
> From your changes, i deduce, that PRId64 and PRIuMAX are
> not defined for y
On 17.10.12 12:35, Maurizio Martignano wrote:
>
> +#ifdef _WIN64
> +Ns_DStringPrintf(dsPtr, "%d %d %d %l64d %l64d %l64d
> %l64d",
> +#else
>Ns_DStringPrintf(dsPtr, "%d %d %d %" PRId64 " %"
> PRId64 " %" PRId64 " %" PRId64,
> +#endif
>
>
> question arise: is this just _WIN64 or a
On Wed, Oct 17, 2012 at 4:55 AM, Maurizio Martignano
wrote:
> OK
>
> Simple reason: Visual Studio complains about that stuff and it is annoying.
Looks like Visual Studio 2012 comes with a C compiler:
http://msdn.microsoft.com/en-us/library/bb384838.aspx
"Visual Studio includes a C compiler th
Dear Gustav,
Thank you for your mail message.
My answer here below.
Maurizio
-Original Message-
From: Gustaf Neumann [mailto:neum...@wu.ac.at]
Sent: 17 October 2012 11:47
To: naviserver-devel@lists.sourceforge.net
Subject: Re: [naviserver-devel] [AOLSERVER] Naviserver Win-64
Maurizio,
the changes you have done are textually quite large, the
patch is 6000 lines +.
Please, don't expect, we can apply this and forget about it,
we need some time
to digest this. Please, don't be impatient, we all have
limited time.
For some problems, it seems for me to be better to foll
Maurizio Martignano wrote:
> OK
>
> Simple reason: Visual Studio complains about that stuff and it is annoying.
> I changed that everywhere. It doesn't do any arm, and for you it is free.
> Why you just do not accept it?
If the problem is that VS is emitting a meaningless warning, I would
first c
OK
Simple reason: Visual Studio complains about that stuff and it is annoying.
I changed that everywhere. It doesn't do any arm, and for you it is free.
Why you just do not accept it?
And the same goes for the keywords "new" and "delete". On the contrary the
keyword "bool" as I already mentioned
On 17.10.2012, at 07:25, Jeff Rogers wrote:
> (could
> users just use a complete tclx, or would that interact badly with signal
> handling or other bits?)
It would.
--
Everyone hates slow websites. So do we.
Make you
Hi Maurizio,
I appreciate your efforts on the windows portability and build front;
but on the issue of c++ acceptability, I think you are trying to do
something that really doesn't need doing.
naviserver/aolserver is written in C. C is not C++. C++ is not "new C"
or "a better C" - it is C++.
Hi everybody,
For those who don't know me, I'm Zoran's partner and am involved
with compiling the Windows version of Tcl and Naviserver at our
company.
As Zoran mentioned in one of his posts, I was reluctant to
release our (my) changes and the VC project files, since those
are quite specific
Dear Maurizio,
First of all, many thanks for your efforts! These are very
welcome!
I am as well somewhat surprised, that there are still pieces
of K&R style around.
There is really no need to keep these. i'll commit an
updated version of tclxkeylist.c
to mercurial. As for the other changes,
16 matches
Mail list logo
