office-gobmx/rsc
Peter Senna Tschudin 3b24dcc8a8 Remove unnecessary semicolons
A simplified version of the semantic match that finds this problem is
follows: (http://coccinelle.lip6.fr/)

// <smpl>
@r1@
statement S;
position p,p1;
@@
S@p1;@p

@script:python r2@
p << r1.p;
p1 << r1.p1;
@@
if p[0].line != p1[0].line_end:
    cocci.include_match(False)
@@
position r1.p;
@@
-;@p
// </smpl>

Change-Id: Ib9708d37fbb4c6060f88d5dae3814a2d37b2091e
Reviewed-on: https://gerrit.libreoffice.org/9493
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>
2014-05-27 01:19:00 -05:00
..
documentation
inc
source Remove unnecessary semicolons 2014-05-27 01:19:00 -05:00
Executable_rsc.mk
Makefile
Module_rsc.mk
README

Resource Compiler.

This compiler converts .src files and .hrc equivalents into binary
.res files.  The basic idea is that this provides a map between
integer identifiers and the resources: string, pixmap (only the
file-name), and VCL control properties.

In more detail:

Typically we would have a .hrc file with entries like this:

#define SID_STR_FOO    1234

And then a .src file with some entries like this:

String SID_STR_FOO
{
    Text [ en-US ] = "Foo !" ;
};

This is compiled into a binary resource file, we have many of these
which live in program/resource/ and then tends to get used in the code
thus:

String aStr( ResId( SID_STR_FOO ) );

It is important to note that any appearance of hierarchical structure
in the .src files is in fact a mirage. The file is compiled at root
into a plain map<integer,resource>.

There is some German documentation about it in a subdirectory called
[git:rsc/doku].  Seems to be very old (January 1992).