On Aug 23, 2010, at 7:00 PM, Roel van Dijk wrote:
> On Mon, Aug 23, 2010 at 8:07 AM, Richard O'Keefe wrote:
>> But what _is_ "the core functionality".
>> The Single Unix Specification can be browsed on-line.
>> There is no part of it labelled "core"; it's all required
>> or it isn't AWK.
[If
On Mon, Aug 23, 2010 at 8:07 AM, Richard O'Keefe wrote:
> But what _is_ "the core functionality".
> The Single Unix Specification can be browsed on-line.
> There is no part of it labelled "core"; it's all required
> or it isn't AWK. There are weird little gotchas like
> File "foo" = '{ pri
On Aug 21, 2010, at 5:14 AM, Michael Litchard wrote:
> Thank you all for your encouragement. I need to think about the core
> functionality, and do some reading.
But what _is_ "the core functionality".
The Single Unix Specification can be browsed on-line.
There is no part of it labelled "core";
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/21/2010 11:22 PM, Bill Atkins wrote:
> I don't think Template Haskell will be essential for this - you
> will probably need a parser (probably written with Parsec), an
> eval function, and a state monad to represent imperative changes
> made by
I don't think Template Haskell will be essential for this - you will probably
need a parser (probably written with Parsec), an eval function, and a state
monad to represent imperative changes made by the language you're evaluating.
Template Haskell is more for the elimination of boilerplate cod
There's a lot of examples of languages implemented in Haskell to choose
from, too
http://haskell.org/haskellwiki/Applications_and_libraries/Compilers_and_interpreters#Large_languages
michael:
> Thank you all for your encouragement. I need to think about the core
> functionality, and do some
Thank you all for your encouragement. I need to think about the core
functionality, and do some reading.
On Fri, Aug 20, 2010 at 2:33 AM, Josef Svenningsson
wrote:
> On Fri, Aug 20, 2010 at 6:05 AM, Jason Dagit wrote:
>>
>>
>> On Thu, Aug 19, 2010 at 8:05 PM, Michael Litchard
>> wrote:
>>>
>>>
On Fri, Aug 20, 2010 at 6:05 AM, Jason Dagit wrote:
>
>
> On Thu, Aug 19, 2010 at 8:05 PM, Michael Litchard wrote:
>
>> I'd like the community to give me feedback on the difficulty level of
>> implementing an awk interpreter. What language features would be
>> required? Specifically I'm hoping th
On 20/08/2010 1:35 PM, Jason Dagit wrote:
fairly easy .. you might want to check out the following tutorial ...
http://www.crsr.net/Programming_Languages/SoftwareTools/ch5.html
he implements a basic grep tool, you might then want to check out one of
the regex packages as a basis for your impleme
On Thu, Aug 19, 2010 at 8:05 PM, Michael Litchard wrote:
> I'd like the community to give me feedback on the difficulty level of
> implementing an awk interpreter. What language features would be
> required? Specifically I'm hoping that TH is not necessary because I'm
> nowhere near that skill lev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/19/2010 11:05 PM, Michael Litchard wrote:
> I'd like the community to give me feedback on the difficulty level of
> implementing an awk interpreter. What language features would be
> required? Specifically I'm hoping that TH is not necessary bec
I'd like the community to give me feedback on the difficulty level of
implementing an awk interpreter. What language features would be
required? Specifically I'm hoping that TH is not necessary because I'm
nowhere near that skill level.
An outline of a possible approach would be appreciated. I am
12 matches
Mail list logo
