head	1.5;
access;
symbols
	FSL_1_0_1:1.4
	FSL_1_0_0:1.4
	FSL_0_9_0:1.4
	CFG_0_9_0:1.4
	FSL_0_1_12:1.4
	FSL_0_1_11:1.4
	FSL_0_1_10:1.4
	FSL_0_1_9:1.4
	FSL_0_1_8:1.4
	FSL_0_1_7:1.4
	FSL_0_1_6:1.4
	FSL_0_1_5:1.4
	FSL_0_1_1:1.4;
locks; strict;
comment	@# @;


1.5
date	2002.08.02.19.07.13;	author rse;	state dead;
branches;
next	1.4;

1.4
date	2002.07.05.20.49.58;	author rse;	state Exp;
branches;
next	1.3;

1.3
date	2002.07.05.18.32.37;	author rse;	state Exp;
branches;
next	1.2;

1.2
date	2002.07.05.14.33.10;	author rse;	state Exp;
branches;
next	1.1;

1.1
date	2002.07.04.14.51.21;	author rse;	state Exp;
branches;
next	;


desc
@@


1.5
log
@full source tree overhauling
@
text
@
foo "<\x40\x41\x42>" "<\x{1404142}>" abd;
bar1 q{ f{o}o } 'foo;' "bar2 bar2b" "foo\nbar" q(foo
bar
quux) "foo\n\r	bar";
quux1 { 
    quux1a; 
    quux1b;
} quux2 {
    q(quu\
    x2a);
    quux2b;
};

@


1.4
log
@More scanner enhancement for supporting Perl-style \x{HHHHHH} sequences
and for better escaping in export output.
@
text
@@


1.3
log
@Add line-continuation support and make export output correctly
quote the tokens.
@
text
@d2 1
a2 1
foo;
d5 1
a5 1
quux);
@


1.2
log
@Add support for Perl-like q(.)[^\1]\1 style quotations which allow one
to place arbitrary stuff into a single syntax token. This is especially
useful if you think about complex OSSP l2 or OSSP pcbe expressions which
else had to be escaped into double- or single-quoted strings in order to
be placed into a OSSP cfg syntax.
@
text
@d3 3
a5 1
bar1 q{ f{o}o } 'foo;' "bar2 bar2b";
d10 2
a11 1
    quux2a;
@


1.1
log
@Flush today's work: the library is now able to parse a .cfg file into
an internal node tree and export this again in textual .cfg file format
(including indented blocks).
@
text
@d3 1
a3 1
bar1 "bar2 bar2b";
@