Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
push lexer?
22 views
Skip to first unread message
Detlef Bosau
Jan 17, 2012, 4:28:57 AM1/17/12
to
Bison 2.5 has a "push api".
http://www.gnu.org/software/bison/manual/html_node/Push-Parser-Function.html
Does there exist something similar for lex of flex or does somebody know
a "push scanner"?
Thanks.
Detlef
[Not that I've ever seen. It would be straightforward to modify flex
to create push lexers that work with push parsers, but so far nobody's
done it. -John]
http://www.gnu.org/software/bison/manual/html_node/Push-Parser-Function.html
Does there exist something similar for lex of flex or does somebody know
a "push scanner"?
Thanks.
Detlef
[Not that I've ever seen. It would be straightforward to modify flex
to create push lexers that work with push parsers, but so far nobody's
done it. -John]
Sven Barth
Jan 17, 2012, 4:00:42 AM1/17/12
to
Am 17.01.2012 05:19, schrieb Paul Robinson:
> Compiling using the DOS IDE, I brought up the file PP.PAS, declared it
> as the primary file, for compiler switches, I entered into the IDE the
> following:
>
> Win32 I386 cpu32bitaddr
>
> Each time it did not find a Pascal Unit I cheated, looked for the file
> and copied it into the 'compiler' dir
ectory rather than try to set the
> directories in the IDE because I was having trouble or doing something
> wrong and it didn't find the files. So then, once it stopped
> complaining, I had it do a 'build' to do a complete scratch build of the
> compiler.
The following command is sufficient to build a compiler for the i386
platform (from inside cmd.exe):
fpc -FUlib -otestpp.exe -FE. -Fusystems -Fui386 -Fux86 -Fii386 -di386 pp.pas
"-FUlib" specifies that all *.o and *.ppu files are generated in
directory "lib" (which you need to create first)
"-otestpp.exe" specifies that the resulting executable should be named
"testpp.exe"
"-FE." tells the compiler that the resulting executable should be
created in teh current directory
"-FuXXX" are the directories which contain other used units
"-FiXXX" specifies directories which contain include files
"-di368" will generate a compiler for "i386". Other possibilities can be
seen in the comments of pp.pas
If you have already compiled the compiler using the Makefile ("make all"
in the top level directory of the FPC source or "make cycle" in the
directory of the compiler) then you can use the "manually" created
compiler to compile itself again using the following command:
testpp.exe -n -Fu{YOURSOURCEDIRECTORY}\rtl\units\i386-win32 -B -FUlib
"-otestpp2.exe" "-FE." -Fusystems -Fui386 -Fux86 -Fii386 -di386 -vinw pp.pas
"-n" tells the compiler not to use its default configuration file
The parameter containing {YOURSOURCEDIRECTORY} is the directory where
the Makefile (see above) compiled the RTL (RunTime Library) to (we need
that now that we don't use the default configuration).
"-B" tells the compiler to recompile all units.
We also use a different name, as "testpp.exe" can not be overriden while
it's running.
"-vinw" tells the compiler to display general information (like
"Compiling blabla.pas"), notes and warnings (this is normally also
included in the default configuration).
Regards,
Sven
> Compiling using the DOS IDE, I brought up the file PP.PAS, declared it
> as the primary file, for compiler switches, I entered into the IDE the
> following:
>
> Win32 I386 cpu32bitaddr
>
> Each time it did not find a Pascal Unit I cheated, looked for the file
> and copied it into the 'compiler' dir
ectory rather than try to set the
> directories in the IDE because I was having trouble or doing something
> wrong and it didn't find the files. So then, once it stopped
> complaining, I had it do a 'build' to do a complete scratch build of the
> compiler.
The following command is sufficient to build a compiler for the i386
platform (from inside cmd.exe):
fpc -FUlib -otestpp.exe -FE. -Fusystems -Fui386 -Fux86 -Fii386 -di386 pp.pas
"-FUlib" specifies that all *.o and *.ppu files are generated in
directory "lib" (which you need to create first)
"-otestpp.exe" specifies that the resulting executable should be named
"testpp.exe"
"-FE." tells the compiler that the resulting executable should be
created in teh current directory
"-FuXXX" are the directories which contain other used units
"-FiXXX" specifies directories which contain include files
"-di368" will generate a compiler for "i386". Other possibilities can be
seen in the comments of pp.pas
If you have already compiled the compiler using the Makefile ("make all"
in the top level directory of the FPC source or "make cycle" in the
directory of the compiler) then you can use the "manually" created
compiler to compile itself again using the following command:
testpp.exe -n -Fu{YOURSOURCEDIRECTORY}\rtl\units\i386-win32 -B -FUlib
"-otestpp2.exe" "-FE." -Fusystems -Fui386 -Fux86 -Fii386 -di386 -vinw pp.pas
"-n" tells the compiler not to use its default configuration file
The parameter containing {YOURSOURCEDIRECTORY} is the directory where
the Makefile (see above) compiled the RTL (RunTime Library) to (we need
that now that we don't use the default configuration).
"-B" tells the compiler to recompile all units.
We also use a different name, as "testpp.exe" can not be overriden while
it's running.
"-vinw" tells the compiler to display general information (like
"Compiling blabla.pas"), notes and warnings (this is normally also
included in the default configuration).
Regards,
Sven
Hans Aberg
Jan 17, 2012, 3:06:08 PM1/17/12
to
On 2012/01/17 10:28, John Levine wrote:
>> Bison 2.5 has a "push api".
>> http://www.gnu.org/software/bison/manual/html_node/Push-Parser-Function.html
>>
>> Does there exist something similar for lex of flex or does somebody know
>> a "push scanner"?
>> Bison 2.5 has a "push api".
>> http://www.gnu.org/software/bison/manual/html_node/Push-Parser-Function.html
>>
>> Does there exist something similar for lex of flex or does somebody know
>> a "push scanner"?
> [Not that I've ever seen. It would be straightforward to modify flex
> to create push lexers that work with push parsers, but so far nobody's
> done it. -John]
FYI, Flex is currently not maintained or developed.
> to create push lexers that work with push parsers, but so far nobody's
> done it. -John]
Hans
[That's true, but it's sitting at Sourceforge, ready for anyone who
wants to pick it up. http://sourceforge.net/projects/flex/ -John]
Johann 'Myrkraverk' Oskarsson
Jan 30, 2012, 6:28:09 PM1/30/12
to
Hans Aberg <haber...@telia.com> writes:
> On 2012/01/17 10:28, John Levine wrote:
>>> Bison 2.5 has a "push api".
>>> http://www.gnu.org/software/bison/manual/html_node/Push-Parser-Function.html
>>>
>>> Does there exist something similar for lex of flex or does
>>> somebody know a "push scanner"?
>
>> [Not that I've ever seen. It would be straightforward to modify
>> flex to create push lexers that work with push parsers, but so far
>> nobody's done it. -John]
>
> FYI, Flex is currently not maintained or developed.
> On 2012/01/17 10:28, John Levine wrote:
>>> Bison 2.5 has a "push api".
>>> http://www.gnu.org/software/bison/manual/html_node/Push-Parser-Function.html
>>>
>>> Does there exist something similar for lex of flex or does
>>> somebody know a "push scanner"?
>
>> [Not that I've ever seen. It would be straightforward to modify
>> flex to create push lexers that work with push parsers, but so far
>> nobody's done it. -John]
>
> FYI, Flex is currently not maintained or developed.
> [That's true, but it's sitting at Sourceforge, ready for anyone who
> wants to pick it up. http://sourceforge.net/projects/flex/ -John]
There is also Reflex, maintained by Thomas Dickey at
> wants to pick it up. http://sourceforge.net/projects/flex/ -John]
http://invisible-island.net/reflex/reflex.html
He is most likely known as the guy behind ncurses and xterm.
I use Reflex among other things because I do use the -P flag too -- it
is broken in SourceForge Flex.
--
Johann Oskarsson http://www.2ndquadrant.com/ |[]
PostgreSQL Development, 24x7 Support, Training and Services --+--
|
Blog: http://my.opera.com/myrkraverk/blog/
0 new messages