On Wed, 4 Apr 2007, William Cox wrote: > so my initial thought is to parse through the main comps source and > pull out what i need (and cache it of course). but this is a bit > brutish IMO. is there useful information from the lexer/compiler that > could be used? or any thoughts on parsing the code?
perldoc HTML::Mason::Plugin You can use the start_component_hook to get at this info really easily. Of course, this only shows what components are actually called at runtime. You could make a compiler subclass easily enough to get the information from the parser, but that wouldn't work in the face of "<& $comp_name &>" -dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
