develooper Front page | perl.perl5.porters | Postings from November 2014

importance, maintainability of ParseXS or the .c code it generates

Thread Next
From:
bulk 88
Date:
November 16, 2014 21:57
Subject:
importance, maintainability of ParseXS or the .c code it generates
Message ID:
COL126-W1887536DD6A059E0F04B5CDF8A0@phx.gbl
What is more important, maintainability of ParseXS.pm's code, or a human being able to read/understand the .c code it generates? Should ParseXS have more complexity to avoid having more complicated/longer C code? (the longer C code is much more efficient/smaller in machine code after compiling than the current state of things) Specifically I plan to have PXS create new scopes/blocks to create/declare  a tmp var, in some cases i dont need to declare a tmp var and i can avoid opening a new scope by reusing RETVAL only if its a SV *, at the cost of more complexity in PXS. Which should i choose? Lets start the bikeshedding.
 		 	   		  
Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About