--- JSON-XS/XS.xs	2008/07/19 04:21:32	1.89
+++ JSON-XS/XS.xs	2009/02/22 06:55:28	1.95
@@ -196,8 +196,8 @@
 {
   if (expect_false (enc->cur + len >= enc->end))
     {
-      STRLEN cur = enc->cur - SvPVX (enc->sv);
-      SvGROW (enc->sv, cur + len + 1);
+      STRLEN cur = enc->cur - (char *)SvPVX (enc->sv);
+      SvGROW (enc->sv, cur + (len < (cur >> 2) ? cur >> 2 : len) + 1);
       enc->cur = SvPVX (enc->sv) + cur;
       enc->end = SvPVX (enc->sv) + SvLEN (enc->sv) - 1;
     }
@@ -282,14 +282,13 @@
                         }
                       else
                         {
-                          static char hexdigit [16] = "0123456789abcdef";
                           need (enc, len += 5);
                           *enc->cur++ = '\\';
                           *enc->cur++ = 'u';
-                          *enc->cur++ = hexdigit [ uch >> 12      ];
-                          *enc->cur++ = hexdigit [(uch >>  8) & 15];
-                          *enc->cur++ = hexdigit [(uch >>  4) & 15];
-                          *enc->cur++ = hexdigit [(uch >>  0) & 15];
+                          *enc->cur++ = PL_hexdigit [ uch >> 12      ];
+                          *enc->cur++ = PL_hexdigit [(uch >>  8) & 15];
+                          *enc->cur++ = PL_hexdigit [(uch >>  4) & 15];
+                          *enc->cur++ = PL_hexdigit [(uch >>  0) & 15];
                         }
 
                       str += clen;
@@ -463,7 +462,7 @@
 
   // for canonical output we have to sort by keys first
   // actually, this is mostly due to the stupid so-called
-  // security workaround added somewhere in 5.8.x.
+  // security workaround added somewhere in 5.8.x
   // that randomises hash orderings
   if (enc->json.flags & F_CANONICAL)
     {
@@ -973,7 +972,11 @@
 
         if (sv)
           {
-            SvGROW (sv, SvCUR (sv) + len + 1);
+            STRLEN cur = SvCUR (sv);
+
+            if (SvLEN (sv) <= cur + len)
+              SvGROW (sv, cur + (len < (cur >> 2) ? cur >> 2 : len) + 1);
+
             memcpy (SvPVX (sv) + SvCUR (sv), buf, len);
             SvCUR_set (sv, SvCUR (sv) + len);
           }
@@ -1413,7 +1416,13 @@
   STRLEN offset;
   SV *sv;
 
-  SvGETMAGIC (string);
+  /* work around bugs in 5.10 where manipulating magic values
+   * will perl ignore the magic in subsequent accesses
+   */
+  /*SvGETMAGIC (string);*/
+  if (SvMAGICAL (string))
+    string = sv_2mortal (newSVsv (string));
+
   SvUPGRADE (string, SVt_PV);
 
   /* work around a bug in perl 5.10, which causes SvCUR to fail an
@@ -1422,12 +1431,17 @@
    * according to nicholas clark, calling SvPOK fixes this.
    * But it doesn't fix it, so try another workaround, call SvPV_nolen
    * and hope for the best.
+   * Damnit, SvPV_nolen still trips over yet another assertion. This
+   * assertion business is seriously broken, try yet another workaround
+   * for the broken -DDEBUGGING.
    */
 #ifdef DEBUGGING
-  SvPV_nolen (string);
+  offset = SvOK (string) ? sv_len (string) : 0;
+#else
+  offset = SvCUR (string);
 #endif
 
-  if (SvCUR (string) > json->max_size && json->max_size)
+  if (offset > json->max_size && json->max_size)
     croak ("attempted decode of JSON text of %lu bytes size, but max_size is set to %lu",
            (unsigned long)SvCUR (string), (unsigned long)json->max_size);
 
@@ -1797,7 +1811,11 @@
             {
               STRLEN len;
               const char *str = SvPV (jsonstr, len);
-              SvGROW (self->incr_text, SvCUR (self->incr_text) + len + 1);
+              STRLEN cur = SvCUR (self->incr_text);
+
+              if (SvLEN (self->incr_text) <= cur + len)
+                SvGROW (self->incr_text, cur + (len < (cur >> 2) ? cur >> 2 : len) + 1);
+
               Move (str, SvEND (self->incr_text), len, char);
               SvCUR_set (self->incr_text, SvCUR (self->incr_text) + len);
               *SvEND (self->incr_text) = 0; // this should basically be a nop, too, but make sure it's there