*) decrypt(char *)
>
> so it can be customized with some limitations
I think using a name other than 'crypt' would be advisable - maybe
php_crypt or something. Otherwise you have a namespace clash with the
usual crypt, which may cause all sorts of grief.
--
Jim Segrave
}
rem -= (loc3 - ptr) + 3;
@@ -388,8 +417,8 @@
while (loc) {
if (!strncmp(loc, boundary, len)
#if NEW_BOUNDARY_CHECK
- && (loc-2>buf && *(loc-2)=='-' &&
*(loc-1)=='-') /* ensure boundary is prefixed with -- */
- && (loc-2==buf || *(loc-3)=='\n') /*
ensure beginning of line */
+ && *(loc-2)=='-' && *(loc-1)=='-' /*
+ensure boundary is prefixed with -- */
+ && *(loc-3)=='\n') /* ensure beginning
+of line */
#endif
) {
break;
--
Jim Segrave [EMAIL PROTECTED]
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
On Fri 01 Mar 2002 (11:00 -0800), Rasmus Lerdorf wrote:
> On Fri, 1 Mar 2002, Jim Segrave wrote:
>
> > > Guys, I fixed this memchr()+1 issue a couple of days ago. See
> > > http://cvs.php.net/diff.php/php4/main/rfc1867.c?r1=1.71.2.2&r2=1.71.2.3&ty=u
&g
I wouldn't suggest that it become part of the distribution.
> We (the MySQL we, that is :) will have a patch shortly. Additionally,
> an upcoming release of MySQL will feature an additional permission to
> control this case.
And this is a much better solution - we'll loo
On Tue 26 Feb 2002 (21:58 +0100), Jim Segrave wrote:
>
> I was looking at the posting from "James E. Flemer" <[EMAIL PROTECTED]>
> and decided to try adding a bit more to it.
>
> ** This code is compiled, but not tested **
I now have a patch against
/* $Id: ph
RETURN_FALSE;
+ }
+ }
+
/* mysql_query is binary unsafe, use mysql_real_query */
#if MYSQL_VERSION_ID > 32199
if (mysql_real_query(&mysql->conn, Z_STRVAL_PP(query), Z_STRLEN_PP(query))!=0)
{
--
Jim Segrave [EMAIL PROTECTED]
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
