On Wed, Mar 10, 2010 at 02:09:41PM +0100, Steffen Mueller wrote: > Marc, if we changed the warning to just appear in case of "INCLUDE: perl > ... |" and to more specifically point to the potentially false > assumption about "perl" being "$^X", would that be an acceptable > solution for you? Of course, this would mean that INCLUDE: ... | would > not be deprecated but just slightly discouraged (via documentation) in > favour of INCLUDE_COMMAND. > > Nicholas, back in the day, you uttered mild disgust at the "INCLUDE: ... > |" construct. Would this trade-off be fine with you, too? Yes. (I can't remember particularly why - I think it's because I thought "It's a file". It's somewhat the same reaction I have to the idea that PDFs would want to contain JavaScript) Seems a very good compromise. Nicholas ClarkThread Previous | Thread Next