text_combined: thomas lee abkvectorsevencom martin v löwis wrote leaves us options 5 reuseabuse numobject arbitrary constants afaict work box eek seem like num would work box would good idea replacing num const might make optimizations specifically numeric values slightly hairier semantically think might different enough warrant separate ast nodes despite similarity implementation compiler level fwiw read num numeric literal const arbitrary constant thats probably ive seen immediate need constants nonnum values process writing ast optimizer 1 new ast expr node constant values types strnum imagine something like constpyobject v effectively translated load_const v compiler trades purity ast little practicality const node real source representation would exist solely purpose injecting pyobject constants ast think way go doesnt violate purity abstract syntax meaning doesnt need 11 relationship source syntax however still possible reproduce source code const node im leaning toward dirt simple quite clean implement also dont worry jython conflicts grammar version number precisely refer specific version need jython folk care weigh major objections think im going forge ahead independant const node cheers _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom fri 08 aug 2008 182417 1000 pythondev optimization python asts deal constant values