If user wishes they can pass the generated code through some nmake-pretty tools. So, +1 for not forcing the code to comply with 80-column rule.
However, we have other formatting issues in generated code which are not related 80-column rule - indentation, extra empty lines etc. - venkat On 7/27/05, Tom Jordahl <[EMAIL PROTECTED]> wrote: > > > > +1 to reverting line breaks in the templates. > > > > Who cares if generated code has 132 character lines? I don't…. > > > -- > Tom Jordahl > Macromedia Server Development > > > ________________________________ > > > From: Ajith Ranabahu [mailto:[EMAIL PROTECTED] > Sent: Monday, July 25, 2005 1:19 AM > To: Axis developer list > Subject: [Axis2] setting the 80 line limit for the XSLT templates > > > > > Hi all, > I find that making the XSL templates confirming to the 80 line standard > generates a problem. Once the transformation is done the generated text > preserves the line breaks in the template. > > For example > > public void receiveResult > <xsl:value-of select="@name"/> creates > public void receiveResult > echoVoid > > public void receiveResult<xsl:value-of select="@name"/> creates > public void receiveResultechoVoid > > (Hope you see the line breaks in the above example) > > Earlier the templates were done in such a manner that the generated code > has line breaks at proper places but the 80 line adjustment made linebreaks > at unwanted places making the code 'uncompilable' . I tried with the > indent='no' option for the transformation but that flag is about 'extra' > line breaks! > If we cannot find a proper solution for this I will sadly have to revert > the line break change in the templates. > > -- > Ajith Ranabahu
