It happened 21 Jun 2007, at 22:51, that Christian Schoenebeck wrote:
Es geschah am Thursday, 21. June 2007 22:15 als Hans Aberg schrieb:
With "intergrated type completion support" I mean a convenient way
for parser
developers (or actually interpreter developers) to let the user
"complete"
the c
Es geschah am Thursday, 21. June 2007 20:18 als Hans Aberg schrieb:
> How should %atomic be implemented?
How it "should" be implemented is the wrong question, or at least addressed to
the wrong person, since I'm not familiar enough with the bison implementation
yet. That was actually my main rea
Es geschah am Thursday, 21. June 2007 22:15 als Hans Aberg schrieb:
> > How it "should" be implemented is the wrong question, or at least
> > addressed to
> > the wrong person, since I'm not familiar enough with the bison
> > implementation
> > yet. That was actually my main reason to write to this
It happened on 21 Jun 2007, at 22:02, that Christian Schoenebeck wrote:
Es geschah am Thursday, 21. June 2007 20:18 als Hans Aberg schrieb:
How should %atomic be implemented?
How it "should" be implemented is the wrong question, or at least
addressed to
the wrong person, since I'm not famil
Es geschah am Thursday, 21. June 2007 20:18 als Hans Aberg schrieb:
> How should %atomic be implemented?
How it "should" be implemented is the wrong question, or at least addressed to
the wrong person, since I'm not familiar enough with the bison implementation
yet. That was actually my main rea
It happened on 21 Jun 2007, at 16:43, that Christian Schoenebeck wrote:
Es geschah am Thursday, 21. June 2007 16:08 als Hans Aberg schrieb:
No, in this model, the lexer matches patterns as usual, only when the
match has been made, returns the multibyte character byte by byte.
Doesn't make a d
On 21 Jun 2007, at 20:07, Fernando Ferreira wrote:
Just another question: is the path to the skeleton hardcoded to
$PREFIX/share/bison/ ? I tried to pass --skeleton="/home/foo/
bar.cc" but it didn't work. Thanks :D
Please to take down the CVS version, as this has changed lately. The
latest
Hans Aberg wrote:
On 21 Jun 2007, at 11:26, Hans Aberg wrote:
In order to make it simple for you, you might add a macro in the
skeleton file. One variation might be (don't remember) to add a macro
something like b4_prereduction_code and then use in the .y file
%define prereduction_code {...}
Es geschah am Thursday, 21. June 2007 16:08 als Hans Aberg schrieb:
> No, in this model, the lexer matches patterns as usual, only when the
> match has been made, returns the multibyte character byte by byte.
Doesn't make a difference. The problem for the UTF-8 part is still the same,
no matter i
It happened on 21 Jun 2007, at 15:43, that Christian Schoenebeck wrote:
Es geschah am Thursday, 21. June 2007 13:12 als Hans Aberg schrieb:
On the one hand, you try to use Bison for something it wasn't
designed for, so unless to can come up with good motivations, getting
the change is unlikely
Es geschah am Thursday, 21. June 2007 13:12 als Hans Aberg schrieb:
> On the one hand, you try to use Bison for something it wasn't
> designed for, so unless to can come up with good motivations, getting
> the change is unlikely to happen.
Depends on which motivation you mean. A motivation for doi
On 21 Jun 2007, at 11:26, Hans Aberg wrote:
In order to make it simple for you, you might add a macro in the
skeleton file. One variation might be (don't remember) to add a
macro something like b4_prereduction_code and then use in the .y
file %define prereduction_code {...} (or %define
On the one hand, you try to use Bison for something it wasn't
designed for, so unless to can come up with good motivations, getting
the change is unlikely to happen. Remember that the development is
done by volunteers that do what they want.
On the other hand, one way to extend Flex & Bison
On 21 Jun 2007, at 08:36, Fernando Ferreira wrote:
Yes, and that would work, but them every time I recompile the .yy
file with bison I would have to manually change the .cc to
include the modification. That's why I think it would be helpful
to have a macro similar to flex' YY_USER_ACTION, s
14 matches
Mail list logo
