quex-general — General Discussion and Announcements

[Quex-general] quex-0.64.8 - demo 003 does not compile

[Sylvain P. <syl...@gm...>]

Hello,


I just tried quex on mac os x (maverick) and I have this error trying to
compile the demo 003:


003 sylvain$ make

clang++  -c -I./ -I/Applications/quex/quex-0.64.8/
-DQUEX_OPTION_ASSERTS_DISABLED -DENCODING_NAME='"UTF8"' -DPRINT_TOKEN
    ../example.cpp -o example.o

In file included from ../example.cpp:5:

In file included from EasyLexer:515:

In file included from
/Applications/quex/quex-0.64.8/quex/code_base/analyzer/headers.i:21:

*/Applications/quex/quex-0.64.8/quex/code_base/analyzer/member/constructor.i:119:24:
**error: *

*      invalid operands to binary expression ('std::istream *' (aka*

*      'basic_istream<char> *') and 'istream' (aka 'basic_istream<char>'))*

    if( p_input_stream == std::cin ) QUEX_ERROR_EXIT(__QUEX_MESSAGE_STDI...

*        ~~~~~~~~~~~~~~ ^  ~~~~~~~~*

1 error generated.

make: *** [example.o] Error 1

I cannot open a ticket neither to post anything on the discussion forums,
so I am using the mailing list.

Best regards,
Sylvain

[Quex-general] Updated documentation

[Saptarshi G. <sap...@gm...>]

Hello,
I notice the online documentation is as of 0.40. If nothing has
changed between 0.40 and 0.47.3, I suppose that is okay,
however if things have would it be possible to update the web documentation?
 Thank you
Saptarshi


Docs: http://quex.sourceforge.net/doc/html/main.html

[Quex-general] String corresponding to yyerror

[Saptarshi G. <sap...@gm...>]

Hello,
Long time back I had emailed this question(I'm posting this to benefit others)


Hello,
Thanks for writing a great tool. Is there a mailing list for this?
I am following demo/008 using Bison together with Quex. In my error function

void Calc_yyerror(quex::Calc_lexer *qlex, const std::string& m)
{
       std::cout << "Parsing error at " << qlex->line_number()
               << ":" << qlex->column_number() << " : " << m;
}

I was hoping if it were possible to get the offending line as a string?
I am calling the lexer as qlex(argc == 1? ... (as in the example), I'm
guessing if I wish to display the offending line I would have to pass
each line to the qlex file?

Regards
Saptarshi


And got this answer:

Note, that if you use a token queue (which is default), you need use
token stamping and get the line number from the token. Otherwise,
please use the token policy 'user's token'. the documentation
elaborates on that.

Frank

Re: [Quex-general] Installation Problems

[Bernhard B. <be...@tz...>]

> I will try the svn version.
It's working fine. Thanks :)

Re: [Quex-general] Installation Problems

[Bernhard B. <be...@tz...>]

Hi Frank,

> [...]
> Please, use the .tar.gz=20
> file which I am going to release at about 10h00 today (Berlin Time).
Should be the same time here in Ludwigsburg :-)
=20
> Concering your idea of implementing quex for different programming
> languages: It is correct I rigidly designed the core engine to=20
> rely on a 'dictionary' that replaces language elements into concrete
> statements dependend on language. However, this design is only
> fulfilled for C and C++. It should be straightforward to get=20
> core analyzers in any language. However, if you want to get the
> full fledged Quex engine including mode handling, etc ... this=20
> requires adaption of the lexer class template, the token queue, and
> the buffer (if you do not want to work on raw memory).
I would like to take a look at the c/c++ version and then decide what I
want to write in Ada (e.g. Text IO is very slow (at least in older Ada
versions)). Ada has got very good c interfacing capabilities.
Sometimes our project [1] is dealing with very huge files (have seen a
130KLoc file) and therefor the speed of the generated lexer is the
most interesting point.

> If there are still problems with 0.14.3 drop me an email under
> fs...@us... with a time that is convenient for
> you and I'll give you a phone number so we can get quex running as
> quick as possible. Are you familiar with svn? This way I could
> do changes and you could update and retest immediately.
I will try the svn version.

kind regards,
Bernhard

[1] http://www.bauhaus-stuttgart.de/bauhaus/

[Quex-general] Installation Problems

[Frank S. <fra...@gm...>]

Hi Bernhard,

your input was very valuable. I configured a new version 0.14.3 which
should fix this issue. In your case your QUEX_PATH variable
should point to "3D/home/berber/quex". Please, use the .tar.gz 
file which I am going to release at about 10h00 today (Berlin Time).

Concering your idea of implementing quex for different programming
languages: It is correct I rigidly designed the core engine to 
rely on a 'dictionary' that replaces language elements into concrete
statements dependend on language. However, this design is only
fulfilled for C and C++. It should be straightforward to get 
core analyzers in any language. However, if you want to get the
full fledged Quex engine including mode handling, etc ... this 
requires adaption of the lexer class template, the token queue, and
the buffer (if you do not want to work on raw memory).

If there are still problems with 0.14.3 drop me an email under
fs...@us... with a time that is convenient for
you and I'll give you a phone number so we can get quex running as
quick as possible. Are you familiar with svn? This way I could
do changes and you could update and retest immediately.


Best Regards,

Frank


-- 
 

Re: [Quex-general] Installation Problems

[Bernhard B. <be...@tz...>]

Hi,

(Disclaimer: Maybe I am trying something that is not supposed to work)

I downloaded the source package of 0.14.2 and unpacked it to ~/quex and
added a link from quex/quex/bin/quex to quex/quex/quex-exe.py

berber@Hitchhiker ~/quex/quex $ ls -lisa bin/quex=20
1922028 0 lrwxrwxrwx 1 berber berber 14 16. Aug 19:18 bin/quex
-> ../quex-exe.py

berber@Hitchhiker ~/quex/quex $ echo $PATH
/home/berber/quex/quex/bin/:...
berber@Hitchhiker ~/quex/quex $ which -a quex
/home/berber/quex/quex/bin/quex

It's sure he finds the "binary" and then I try to set QUEX_PATH and
call quex.

berber@Hitchhiker ~/quex/quex $ export QUEX_PATH=3D/home/berber/quex
berber@Hitchhiker ~/quex/quex $ quex
Traceback (most recent call last):
  File "/home/berber/quex/quex/bin/quex", line 25, in ?
    import quex.input.setup as setup_parser
  File "/mnt/dist/home/berber/quex/quex/quex/input/setup.py", line 7,
in ? from frs_py.string_handling import trim
ImportError: No module named frs_py.string_handling

berber@Hitchhiker ~/quex/quex $ export QUEX_PATH=3D/home/berber/quex/quex/
berber@Hitchhiker ~/quex/quex $ quex
Traceback (most recent call last):
  File "/home/berber/quex/quex/bin/quex", line 25, in ?
    import quex.input.setup as setup_parser
  File "/mnt/dist/home/berber/quex/quex/quex/input/setup.py", line 7,
in ? from frs_py.string_handling import trim
ImportError: No module named frs_py.string_handling

berber@Hitchhiker ~/quex/quex $ export
QUEX_PATH=3D/home/berber/quex/quex/quex

berber@Hitchhiker ~/quex/quex $
quex error: no input files
Traceback (most recent call last):
  File "/home/berber/quex/quex/bin/quex", line 33, in ?
    core.do(setup)
  File "/mnt/dist/home/berber/quex/quex/quex/core.py", line 37, in do
    sys.exit(-1)
NameError: global name 'sys' is not defined
=20
After adding the missing import quex starts without an exception:
berber@Hitchhiker ~/quex/quex $ quex
error: no input files

And now the first demo:
berber@Hitchhiker ~/quex/quex $ cd demo/000/
berber@Hitchhiker ~/quex/quex/demo/000 $ make
quex --mode-files simple.qx    \
             --engine     tiny_lexer=20
warning: no initial mode defined via 'start'
warning: using mode 'ONE_AND_ONLY' as initial mode
## 1
error: opening file
'/home/berber/quex/quex/quex/quex/code_base/template/count_line_column.i'
failed

the problem is that there is a quex too much in the path (or the
QUEX_PATH is wrong) after making a softlink:
berber@Hitchhiker ~/quex/quex/demo/000 $ make
quex --mode-files simple.qx    \
             --engine     tiny_lexer=20
warning: no initial mode defined via 'start'
warning: using mode 'ONE_AND_ONLY' as initial mode
## 1
error: empty token-id list. quex cannot proceed.
error: use the 'token { ... }' section to specify at least one token id.
make: *** [tiny_lexer] Fehler 255

What did I do wrong?=20
Bernhard

[Quex-general] Sorry for unintended mail deletion!

[Frank S. <fra...@gm...>]

As the previous mail indicates, I'm still tampering with the setup
of the mailing list. As a consequence of a unadverted click, I deleted
mail '1' of this list. Sorry!
-- 
// Dr.-Ing. Frank-René Schäfer, Bodelschwinghstr. 28
// D-50170 Kerpen
// Tel.: 49+176/22 02 58 59; 

[Quex-general] Fwd: Installation Problems II

[Frank S. <fra...@gm...>]

Sorry, for the unsorted mailing list. I am still in the process of
understanding how to set this up propperly ...

Concerning your Berhards installation problem, there should be
no "--engine tiny_lexer=20" option in any example makefile.
Please, send me simple.qx and Makefile from quex/demo/000.


-------- Original-Nachricht --------
Datum: Wed, 15 Aug 2007 23:21:10 -0700
Von: que...@li...
An: que...@li...
Betreff: Quex-general post from fra...@gm... requires approval

> As list administrator, your authorization is requested for the
> following mailing list posting:
> 
>     List:    Que...@li...
>     From:    fra...@gm...
>     Subject: Installation Problems
>     Reason:  Post by non-member to a members-only list
> 
> At your convenience, visit:
> 
>     https://lists.sourceforge.net/lists/admindb/quex-general
>         
> to approve or deny the request.

-- 
// Dr.-Ing. Frank-René Schäfer, Bodelschwinghstr. 28
// D-50170 Kerpen
// Tel.: 49+176/22 02 58 59; 

[Quex-general] Installation Problems

[Frank S. <fra...@gm...>]

Hi Bernhard,

There were serious Problems that the installation builder had with
symbolic links. Installing Quex by hand should not be a big deal.
As you said, the only thing to do is to add a link from a 
place where your system finds executables to quex-exe.py and
making it exectable. Make sure that you define QUEX_PATH propperly
and pass -$(QUEX_PATH) to the compiler. Also, if you are using 
a compiler different from g++ you might want to modify the 
make files.

Please, send me some output or screenshots if things still do not
work out. Also, I would advice you to use version 0.14.2, since
it has fixed a bug concerning the automatic wchar_t conversion.
I am running quex on linux, too--and I do not release without
all unit tests passed.

Best Regards

Frank