Proposed feature: #include inline
"R. Tyler Ballance" <[email protected]> Tue, 14 Jul 2009 16:47:18 -0700
| Newsgroups | gmane.comp.python.cheetah |
|---|---|
| Message-ID | <[email protected]> |
I'm not going to write up a CHEP for this just yet, but I came across a usecase for `#include inline` version `#include raw` today. When watching a production server run through a particular template I realized that we were using `#include raw` far too much, resulting in a large amount of open(2) and read(2) calls (to be expected, duh). What we *really* want to do however, is an `#include inline` which would be processed and the contents of the included file inlined at *compile time* instead of raw's inclusion at run time. Thoughts? Tavis, if you've no enormous objections, I think this would be a reasonable addition. Cheers -R. Tyler Ballance Slide, Inc. ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Cheetahtemplate-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cheetahtemplate-discuss
signature.asc
(application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkpdGOkACgkQFCbH3D9R4W8CkQCgleES8yMCPsB+xfV3+viGCAPB SFUAn0qrrF9YKh77mcNG/wYXVUncjJ3y =HOq1 -----END PGP SIGNATURE-----