Well, I think that checking for a newline at the end of an #included
file and adding if not there would help stop some bugs.

I've modified the UDO repository to now add a newline at the end of
the generated files, so I think at least that will be correct now.

steven

On 10/31/05, Istvan Varga <istvan_v@fibermail.hu> wrote:
> Steven Yi wrote:
>
> > Been in a self management mode today and organizing things and saw
> > this email.  Is this bug with #includes and no newlines at end of file
> > still causing a bug?
>
> I did some tests, and it seems that problems occur only if the included
> file does not have a newline at the end at all, rather than requiring an
> extra blank line. So, I am not sure if this is really a bug, as files
> should be correctly terminated.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.
> Get Certified Today * Register for a JBoss Training Course
> Free Certification Exam for All Training Attendees Through End of 2005
> Visit http://www.jboss.com/services/certification for more information
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net