log4perl-devel

[log4perl-devel] extension lines in ConversionPattern?

[Dintelmann, P. <Pet...@Dr...>]

Hi,

can we have extension lines in ConversionPatterns? I just wrote

    log4j.appender.BLA.layout.ConversionPattern=Time:   %d%nHost:   %H%nPID:
%P%n%nLevel:  %p%nSource: %c%n%n%m%n
    
in a config file which is nearly unreadable in a standard terminal. I'd
rather like to see

    log4j.appender.BLA.layout.ConversionPattern=Time:   %d%nHost:   %H%n\
    PID:    %P%n%nLevel:  %p%nSource: %c%n%n%m%n
    
instead, where the \ at end of line extends it to the next line. 

This improves readability from my point of view.

Regards,

    Peter Dintelmann

--
Dr. Peter Dintelmann
Dresdner Bank AG
CC IT MIS - MIS@ Products
Theodor-Heuss-Allee 110
D-60301 Frankfurt
Germany

Tel.:  +49-(0)69-263-19722
Email: Pet...@dr...

http://www.dresdner-bank.com
http://mis.dresdner-bank.com

Re: [log4perl-devel] extension lines in ConversionPattern?

[Kevin G. <ke...@go...>]

 > can we have extension lines in ConversionPatterns? I just wrote

Sure, they've been accepted for a while.  You do just about anything

      log4j.appender.BLA.layout.ConversionPattern=Time:   \
			%d\
			%n\
			Host:   %H\
			%nPID: %P%n%nLevel:  %p\
			%nSource: %c%n%n\
			%m%n


Keep in mind if the config is in perl, like in a here-doc, you have to
either single-quote it or use double backslashes.  And also that the 
continuation line cleaver eliminates whitespace on continuation lines up 
to the first whitespace character, so
	foo\
	bar
will come out 'foobar', while
	foo \
	bar
will come out 'foo bar'.


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217