Hipo has quit [Read error: 104 (Connection reset by peer)]
Hipo has joined #ocaml
wazze has quit ["Learning about how the end letters on French words are just becoming more and more silent, I conclude that one day the French]
reltuk has quit ["sleeping"]
Nutssh has joined #ocaml
Nutssh has quit [Client Quit]
ott has joined #ocaml
<ott>
re all
<DiabloEMN>
'
<async>
what's all the fuss with scala
d2004xx has joined #ocaml
d2004xx has left #ocaml []
karryall has joined #ocaml
Swynndla has quit ["Leaving"]
ott has quit ["BitchX-1.0c16 -- just do it."]
ott has joined #ocaml
vect has quit ["[BX] Showering in your clothes shows you're crazy. Showering nude shows your nuts."]
vect has joined #ocaml
gim__ has quit [Remote closed the connection]
<vect>
yoooo
<karryall>
vect: yoooo
_JusSx_ has joined #ocaml
_JusSx_ has left #ocaml []
_JusSx_ has joined #ocaml
<DiabloEMN>
yo!
<pattern>
hmmm... i didn't know "functional programming" was synonymous with "applicative programming"
<pattern>
i don't hear the latter term used much
mimosa has joined #ocaml
Nomme has joined #ocaml
<Nomme>
hi
<karryall>
pattern: me neither
cjohnson has joined #ocaml
<pattern>
another curious factoid was that ml was invented to program a theorem prover, the Edinburgh LCF
<pattern>
didn't know that either
housetier has quit [Read error: 110 (Connection timed out)]
Banana[Home] has joined #ocaml
Banana[Home] is now known as Banana
<det>
pattern: function != applicative
<det>
pattern: joy is a functional concatonative language
<det>
pattern: ML, haskell, lambda-calulus, etc are function applicative ones
<pattern>
interesting
gim|570 has joined #ocaml
gim has quit [Read error: 104 (Connection reset by peer)]
smklsmkl has joined #ocaml
smkl has quit [Read error: 110 (Connection timed out)]
Etaoin has joined #ocaml
ott has quit ["ott has no reason"]
mr_jim has joined #ocaml
mr_jim has quit ["Leaving"]
Keltus has joined #ocaml
<Nomme>
is there a tool (like ocamldep) to have the link order of the object ?
<karryall>
Nomme: ocamldsort
<Nomme>
thank
Banana has left #ocaml []
Banana[Home] has joined #ocaml
karryall has quit ["g"]
_JusSx_ has quit ["[BX] If idiots could fly, IRC would be an airport"]
mr_jim has joined #ocaml
mr_jim has quit ["Leaving"]
_JusSx_ has joined #ocaml
wazze has joined #ocaml
<Nomme>
with ocamlyacc what's a shift/reduce conflict ?
<Nomme>
how can i solve it ?
__DL__ has joined #ocaml
<Nomme>
hello __DL__
* Nomme
very nic
<Nomme>
*nice
<mattam>
Nomme: you should read something about grammars i think :)
<Nomme>
yes, you're right :/
<Nomme>
I learn english only since 8 years
<mattam>
basically a shift reduce conflict means there's somewhere in your grammar where the parser could either reduce the parsed data (ie return from a rule) or continue parsing (it is inside a rule but not at the end of a particular case) and the choice cannot be made when reading just 1 token more (the 1 in LALR(1), which is the class of grammars parsed by yacc/ocamlyacc, describe this lookahead)
<mattam>
you can use ocamlyacc -v parser.mly and look at the end of parser.output for information about the rules involved.
<__DL__>
hello
<vect>
yoooo
<vect>
da fr3nch cr3w is in d4 place !
<vect>
ahem.
<Nomme>
ok
<__DL__>
well, it seem we are often here at the same time of the day...
<Nomme>
is it normal to find a such conflict in scheme's grammar ?
<__DL__>
well, a shift/reduce conflict ? I belive that scheme (and lisp) gramar should be free from those.
<__DL__>
(but there are some in the caml gramar if you want an example
<__DL__>
)
<Nomme>
i am not able to correct it, could you help me ?
<Nomme>
(i'll understand if you haven't time or if you find this boring)
<__DL__>
i can give it a look
<__DL__>
(and I may stand corrected if there is one for a good raison...)
<Nomme>
<Nomme> this expression isn't parse correctly "(lambda (x) (define y 2) (f x y))"
gim|570 has quit [Connection reset by peer]
<__DL__>
well, it seem stragne that nobody speak on #debian... I've understood now....
<Nomme>
:)
<__DL__>
"je sais plus" is a very bas cvs message log :)
<Nomme>
yes :)
<Nomme>
there isn't many comments
<Nomme>
there are... :)
<__DL__>
well, the shift/reduce conflict is here, whith no dout, and provoc a failure to parse "(lambda (x) (define y 2) (f x y))"
<Nomme>
is it possible to solve it ?
<mimosa>
Nomme: have you tried ocamlyacc -v ?
<__DL__>
here the pb : when he have read "(lambda (x) (define y 2) " he must decide if the define_list is finish or not, and to make its decision, he can only look to (f x y)
<mimosa>
(I just came back so maybe am I "à côté de la plaque")
<__DL__>
the solution for this kind of pb : make a more permisive gramar, then fail afterward in the reduction action
<Nomme>
i don't choose the grammar
<Nomme>
(mimose: i have tried but it's chinese for me :'()
Nutssh has quit ["Client exiting"]
Hadaka has quit [Connection refused]
<Nomme>
i'll never be conform to R5RS :/
<__DL__>
you can alway choose your gramar.
<Nomme>
there is a standard
<__DL__>
the solution is to provoque an artificial error in the action (that is in the {...} thingy) and not in the ocamlyacc generated code.
Hadaka has joined #ocaml
<mimosa>
I think you should try to solve the shift reduce
<Nomme>
an artificial error ?
<mimosa>
by trying to find a term which could be interpreted in tow different manners
<mimosa>
if you've got 2 definitions : definition definition
<mimosa>
it can be seen as one definition list
<Nomme>
yes, and ?
<Nomme>
i don't fallow you
<Nomme>
(is it english ? :))
<__DL__>
its follow.
<__DL__>
Well, I neither, but I've seen an interestin solution :
<__DL__>
body : expr_list | declaraion body
Nutssh has joined #ocaml
<__DL__>
(that is a body is either an expr_list or a delcaration followed by a body)
<__DL__>
of course this is less beatifull, but it is LALR.
<Nomme>
LALR ?
<ita>
take a grammar tutorial dude :)
<__DL__>
your gramar have to be an LALR(1) grammar to be understood by ocamlyacc
<Nomme>
ok
<Nomme>
i see
<Nomme>
i haven't yet seen language theory at university, :/
<Nomme>
i haven(t seen yet
<__DL__>
there are tutorial on the net for sure.
<DiabloEMN>
qq1 a la capacit? du laiton?
<Nomme>
google is my friend :)
<Nomme>
is laiton a pokemon ?
<DiabloEMN>
sorry, it shouldn't have posted this message on this chan...
<Nomme>
:)
<DiabloEMN>
I made a amsg I didnot think I would post on another server...
mattam_ has joined #ocaml
<Nomme>
the conflict still occurs :/
<__DL__>
same one ? look at the end of the .output, it say where is the conflict (in what stat), then look to this state, it give you an hit of where it is in the grammar.
blueshoe has joined #ocaml
<Nomme>
yes
<Nomme>
exactly the same
<Nomme>
sorry
<Nomme>
no, no
<mimosa>
I had things to do sorry Nomme for not having finished my answer but anyway your problem seems to have been solved
<Nomme>
he's left :)
ita has quit [Remote closed the connection]
<__DL__>
Strange because with my solution, there isno declaration list anymore, or is it used somewhere else ?
<mimosa>
oh no
<Nomme>
thank both of you
<Nomme>
__DL__, no, no it's ok now
<mimosa>
Nomme: you should try to learn how to read the .output (at least roughly) it can be useful
<mimosa>
50: shift/reduce conflict (shift 65, reduce 17) on Lpar