Olga, This is off the topic but I'm really interested in the last bit "Python shell integration". How do you see Python fit in Pig?
Cheers, Pi On 3/4/08, Olga Natkovich <[EMAIL PROTECTED]> wrote: > > Stefan, > > The main reason is that, why we would always be parsing pig statement > within Pig, for shell we might choose a completely different environment > like integration into the Python shell so we probably don't want to put > two together. > > Olga > > > -----Original Message----- > > From: Stefan Groschupf [mailto:[EMAIL PROTECTED] > > Sent: Friday, February 29, 2008 6:15 PM > > To: [email protected] > > Subject: Re: pigScriptParser > > > > Olga, > > thanks for the clarification. > > > We have a 2 level parser: > > > > > > Grunt parser handles all commands other than Pig commands > > and passes > > > Pig commands to the pig parser. To do so, it needs to parse the pig > > > command enough to figure out that it needs to go to pig parser. > > > > Why does pig has two parsers? Even if I use embedded pig the > > pig latin is the same as in grunt, isn't it? > > Isn't that more overhead of maintain two javacc files? > > > > Stefan > > > > >
