Re: Byte-compiling the line specs

[larsi@ifi.uio.no (Lars Magne Ingebrigtsen)]

Felix Lee <flee@teleport.com> writes:

> so, umm, I'll try gc monitoring soon.  but really, the best test is to
> write a full-blown format-string compiler and see how it performs in
> live cases.

Definitely.  These timings are interesting, but `(princ 99999)' isn't
a very realistic element resulting from a line spec.  There's lots of
"%5d"s (etc) but no "%d"s.  I'd be very interested in seeing timings
resulting from transforming:

(insert
 (progn
   (insert
    (format "%c%c%c%s " gnus-tmp-unread gnus-tmp-replied gnus-tmp-score-char gnus-tmp-indentation))
   (let
       ((b
	 (point)))
     (insert
      (format "%c%4d: %-20s%c" gnus-tmp-opening-bracket gnus-tmp-lines
	      (let*
		  ((val
		    (eval gnus-tmp-name))
		   (valstr
		    (if
			(numberp val)
			(int-to-string val)
		      val)))
		(if
		    (>
		     (length valstr)
		     20)
		    (substring valstr 0 20)
		  valstr))
	      gnus-tmp-closing-bracket))
     (put-text-property b
			(point)
			'mouse-face gnus-mouse-face))
   (insert
    (format " %s\n" gnus-tmp-subject-or-nil))))

-- 
Home is where the cat is.