Do we need `CHEP` documents?

I've been kicking around the idea the past couple weekends about how to
handle growing Cheetah as a domain specific language for templating and
text manipulation (let's face it, that's what Cheetah really is ;)).

The notion of the 'CHEP' (similar to the Python PEP) has come to mind as
a way of explaining and vetting possible language features by the
community in a similar fashion to how Python PEPs are handled/evolved.


I'll likely write up a CHEP for some inheritance plans that I have
(exposing $self, allowing for true $super() calls, etc) in the coming
weeks, but I wanted to see if anybody else had any suggestions for
handling this.


Cheers
-- 
-R. Tyler Ballance
Slide, Inc.

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects

_______________________________________________
Cheetahtemplate-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cheetahtemplate-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkoPJx8ACgkQFCbH3D9R4W+/MgCdFgbcYBuTdxqf/ItHxlgfyDMS
vzcAnA2thondGFVffE7o9ZrqWij+2XPX
=uqZP
-----END PGP SIGNATURE-----