Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Alternatives to sed + awk
- Date: Fri, 11 Mar 2011 08:49:28 +0000
- From: Simon Cozens <simon@example.com>
- Subject: Re: [tlug] Alternatives to sed + awk
- References: <AANLkTim_-D9CFYC8TNp33ni85zB+QBA7jV=BpLN=4SbZ@example.com> <4D6F8D94.9040109@example.com> <87ei6nl906.fsf@example.com> <AANLkTimk1z41fSvQQmU+7fE-1Krd_kuo3_z-1SYD5rW6@example.com> <87ipvskik1.fsf@example.com> <AANLkTi=_6DoBt+xfQVOwM6KyKrxxgA_Ec9bhp751f15y@example.com> <8762rsjkdx.fsf@example.com> <AANLkTik=tHOgTRvcvNd0qsx9-o9MuqBnWUjkWVn+0U_7@example.com> <4D793EDF.2090308@example.com> <87oc5iqnuk.fsf@example.com>
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b10pre) Gecko/20110114 Thunderbird/3.3a2
On 11/03/2011 04:32, Stephen J. Turnbull wrote: > So real > attempts at DSLs in Lisp will either display a lot of Lisp syntax, or > have a separate lex/parse stage like Maxima does. Well, this is exactly my (and chromatic)'s point. People have been throwing the DSL label onto things which are clearly not DSLs, and I'd say your example is a borderline case. It's a domain specific language for specifying loops, sure, *so long as* the content of those loops happens to be LISP code. In other words, if you have someone who's an absolute expert on specifying loops (whatever that might mean) they'll find this a great, expressive way of specifying a loop, but they'll still have to hand over to a LISP programmer to put some LISP code in the middle. To my mind this makes it a language extension, not a DSL in its own right. The most I'm prepared to say is that it's a DSL for a domain that's so incomplete that you can't do anything useful with it at all. I agree with what you're saying - your choices are: (a) a clean DSL without a parser but which can't do anything interesting, (b) a "dirty" DSL without a parser that's so embedded in a higher-level programming language that you force your domain experts to learn the syntax and semantics of that language, or (c) write your own parser and do it properly, dammit, then you get to call it a DSL. When the Ruby folks say "we can write DSLs without a parser", what they mean is option (b), "we can write DSLs that display a lot of Ruby syntax without a parser", and therefore what they're actually saying is "we can write subroutines." S
- Follow-Ups:
- Re: [tlug] Alternatives to sed + awk
- From: Josh Glover
- Re: [tlug] Alternatives to sed + awk
- From: Stephen J. Turnbull
- References:
- [tlug] Alternatives to sed + awk
- From: Nguyen Vu Hung
- Re: [tlug] Alternatives to sed + awk
- From: Alexander Danilov
- Re: [tlug] Alternatives to sed + awk
- From: Stephen J. Turnbull
- Re: [tlug] Alternatives to sed + awk
- From: Alexander Danilov
- Re: [tlug] Alternatives to sed + awk
- From: Stephen J. Turnbull
- Re: [tlug] Alternatives to sed + awk
- From: Josh Glover
- Re: [tlug] Alternatives to sed + awk
- From: Stephen J. Turnbull
- Re: [tlug] Alternatives to sed + awk
- From: Josh Glover
- Re: [tlug] Alternatives to sed + awk
- From: Simon Cozens
- Re: [tlug] Alternatives to sed + awk
- From: Stephen J. Turnbull
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Hope everone is ok
- Next by Date: Re: [tlug] Hope everone is ok
- Previous by thread: Re: [tlug] Alternatives to sed + awk
- Next by thread: Re: [tlug] Alternatives to sed + awk
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links