Hello,
I added the -Wall option to CFLAGS, and I add a lot of warnings. I know
this doesn't mean that there are errors, but it could hide some. Maybe
it would be nice to enable this flag and to try to correct some of these
warnings don't you think ?
Regards,
--
Colin Pitrat (Bull Services
On Thu, 2006-10-12 at 10:03 +0200, Colin Pitrat wrote:
I added the -Wall option to CFLAGS, and I add a lot of warnings. I know
this doesn't mean that there are errors, but it could hide some. Maybe
it would be nice to enable this flag and to try to correct some of these
warnings don't you
Great idea !
We are waiting such a patch from you!
regards
Vincent
- Original Message -
From: Colin Pitrat [EMAIL PROTECTED]
To: devel@kannel.org
Sent: Thursday, October 12, 2006 10:03 AM
Subject: Compiling kannel with -Wall option
Hello,
I added the -Wall option to CFLAGS, and I
Alex,
Your patch looks incomplete (ie smsbox part as you already knows)
Actually we have a little compatibility breaker on charset I/O.
Could you please complete this, and set the default as latin1
(or clearly indicates here a compatibility breaker)
Also, the userguide need to be updated.
We did that once for our own application which is using gwlib.
Its just a lot of hand work and quite a few typecasts.
One problem spotted while doing that is that gwlib is never sure if
an octet from an octetstring should be considered a signed char or a
unsigned char. My personal view is
Hi Vincent,
I would like to keep UTF-8 as default charset. So we can send any charset
we want w/o any troubles. I agree that we should document it in userguide.
For users that want further send in latin1: they can use 'charset=LATIN1'
cgi parameter for sendsms interface.
What others
On Thu, 2006-10-12 at 13:27 +0200, Alexander Malysh wrote:
I would like to keep UTF-8 as default charset. So we can send any charset
we want w/o any troubles. I agree that we should document it in userguide.
For users that want further send in latin1: they can use 'charset=LATIN1'
cgi
Alexander Malysh wrote:
Hi Vincent,
I would like to keep UTF-8 as default charset. So we can send any
charset we want w/o any troubles. I agree that we should document it in
userguide. For users that want further send in latin1: they can use
'charset=LATIN1' cgi parameter for sendsms
before (MO)
E50_NMSG
2852453A2950657572206465206D61207205616374696F6E2070617320726170706F7274207F2071756F693F
E50_AMSG(RE:)Peur de ma réaction pas rapport à quoi?
E50_TMSG(RE:)Peur de ma réaction pas rapport à quoi?
before (DLR)
E50_NMSG
Vincent CHAVANIS wrote:
before (MO)
E50_NMSG
2852453A2950657572206465206D61207205616374696F6E2070617320726170706F7274207F2071756F693F
E50_AMSG(RE:)Peur de ma réaction pas rapport à quoi?
E50_TMSG(RE:)Peur de ma réaction pas rapport à quoi?
before (DLR)
E50_NMSG
Vincent CHAVANIS wrote:
Here is a new version in my devel cvs tree, a bit more verbose in debug
-logs for aliases and services names
-logs when executing get_matching_translations() and return an empty list
commited to cvs, but without he last debug() line, since this is an add-on...
11 matches
Mail list logo