similar to: Sieve regex match problem

I'm getting a core dump with the following script: require [ "fileinto", "regex", "variables" ]; if address :domain :regex ["Reply-To", "Sender", "To", "Cc"] "antlr.org|mailman.unixodbc.org|research.att.com|wireshark.org" { if address :regex ["Reply-To", "Sender", "To",

When you create a parser via ANTLR you specify the output language of the resulting recursive descent parser, at the moment there exists no C++ output template to my knowledge, thus you would have to generate the parser as C code for which a template exists. The runtime support should be there, at least partially but it won't use things like exceptions, nor will it have a very modular design

Hi, I've not got any experience using ANTLR to parse C++, however, you will find that there only exists a C code generator for ANTLR and NOT a C++ one. Over the years numerous people have requested a C++ code generation template but alas there is still only a C one. Just a heads up. Granville 2009/7/11 Vikram S. Adve <vadve at cs.uiuc.edu> > We are looking for an open source C++

Hello, I've been trying out the bleeding edge, 1.2.alpha4. I'm having a problem with deliver and dovecot-1.2-sieve-0.1.1. I get a segv on this sieve script: require ["fileinto", "reject", "vacation", "envelope", "regex"]; if header :contains "subject" ["urgent"] { redirect "someone at somewhere.net";

That sounds like a problem. Just so I understand, do you mean there isn't the run-time support etc. to write back ends for the C++ language, or that the compiler IR is also somehow insufficient to write a code generator? --Vikram Associate Professor, Computer Science University of Illinois at Urbana-Champaign http://llvm.org/~vadve On Jul 11, 2009, at 3:00 PM, Granville Barnett

On 20 Mar 2007, at 15:45, Jeff Cohen wrote: > Duncan Sands wrote: >>> If that fails, I will build a front-end using ANTLR [http:// >>> antlr.org] a parser generator with which I am familiar and for >>> which a FORTRAN grammar is already available (targeting an >>> obsolete version of ANTLR, but it should not be too difficult to >>> update).

For a LL(1) parser, it might be a little bit difficult to parse complex grammar like C++, but it might work. ANTLR worked great when other codes were written in Java, but it was a little bit painful when using other languages like python. I worked on it two years ago. I guess they might have some improvement now. Haohui On 07/11/2009 02:40 PM, Vikram S. Adve wrote: > We are looking for an

Duncan Sands wrote: >> If that fails, I will build a >> front-end using ANTLR [http://antlr.org] a parser generator with which >> I am familiar and for which a FORTRAN grammar is already available >> (targeting an obsolete version of ANTLR, but it should not be too >> difficult to update). >> > > Bad plan. I doubt you can build a serious fortran

Hi Scott, I'm currently porting the Ada gcc front-end to LLVM. This is similar to what you want to do, so here are some comments from the trenches... > I plan on first attempting to implement the FORTRAN front-end by > co-opting the GCC FORTRAN parser. Good plan. However the Fortran front-end that comes with gcc 4.0 is known to be weak (llvm-gcc is based on gcc 4.0). That's

Has anyone written a grammar for LLVM for ANTLR. I mean an ANTLR grammar that parses LLVM instructions. Is an LLVM grammar available for any other parsing tool? Surinder

On Jul 11, 2009, at 12:40 PM, Vikram S. Adve wrote: > We are looking for an open source C++ parser other than g++ if > possible. Clang would be great but its C++ support is still some > way away and we need something that works or nearly works now. Does > anyone have any experience with ANTLR for parsing C++ and for > extending their C++ parser? Any other feedback on

Hi! I have to import some TXT files into R, but the separation between the columns are made with different blank spaces, but each file use the same separation. Example: 31 104 5 0 11RUA SAO SEBASTIAO 25 BAIRRO FILETO 01

Hi Sam, Thanks for your reply. I am implementing my research (http://www.it.usyd.edu.au/~suri/Detecting%20Buffer%20Over.pdf), a translation of LLVM to a simple non-deterministic language to detect buffer overflows. It involves (1) printing a control flow graph of basic blocks of a function (easily done) (2) translating each llvm statement to a corresponding data flow language (needs ASTs to

Hello Surinder, The existing hand-written parser is callable from almost anywhere so the only reason you'd need to have a parser for it would be to extend it. Originally it was written using Flex and Bison but Chris Lattner rewrote it from scratch to catch more errors at the parsing stage. The only feature I've found to be missing from the existing LLVM-AS utility was an include

We are looking for an open source C++ parser other than g++ if possible. Clang would be great but its C++ support is still some way away and we need something that works or nearly works now. Does anyone have any experience with ANTLR for parsing C++ and for extending their C++ parser? Any other feedback on ANTLR in general would be welcome too. Thanks, --Vikram Associate Professor,

Right, I understand that. I was hoping there was such an implementation using ANTLR since it looks like a fairly mature project. I'm not sure how stable or mature Elsa is (but comments to clarify that would be appreciated.). E.g., a quick scan of their Web page shows the comment that they only have a partial type checker. It also says their template instantiation is incomplete.

Hello, is the LDA linked against the Cyrus SIEVE library or against the fork at libsieve.sourceforge.net ? It seems Cyrus SIEVE from src/libsieve/README in the lda sources. libsieve seems to be better suited for inclusion in non-cyrus software and should be completely independent from libcyrus. The README for cyrus version of libsieve also states that: "It should compile without libcyrus,

I've done extensive research on the subject and if you want to parse ALL of C++, there are only two options, g++ or the Edison Design Group C++ front-end. Both of these have projects designed to make this easier LLVM (as you know) and Rose (http://www.rosecompiler.org/), which works with the EDG compiler. AspectC++, OpenC++, Antler, TLX, all work with only a portion of the grammer. On Sat,

Am building sieve plugin on AIX. This is revision 1095:8010f1eb66b3. I see the following error when doing the build: rm -fr .libs/lib90_sieve_plugin.lax^M mkdir .libs/lib90_sieve_plugin.lax^M rm -fr .libs/lib90_sieve_plugin.lax/libsieve.a^M mkdir .libs/lib90_sieve_plugin.lax/libsieve.a^M (cd .libs/lib90_sieve_plugin.lax/libsieve.a && ar x /usr/sadmin/src/

Hi, the dovecot-sieve plugin from the hg repository (http://hg.dovecot.org/dovecot-sieve-1.0/) does not build against current dovecot-1.0 repository. /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -DENABLE_REGEX -o sievec sievec.o map.o imparse.o