In reading things, we exclude the impossible. For example, when you
read "He sold the dog biscuits", you may not even notice there are two
parses, because the second one has the dog being the buyer of the
biscuits and we know that's impossible -- dogs, much as they love
biscuits, have to rely on others to buy them.
Many have come to believe over the years that a practical parser that
can efficiently handle a very wide variety of syntax was just not a real
possibility -- not gonna happen. I think a lot of people are reading my
blog posts in terms of the "possible" and missing what I'm saying. I
think that is a big issue for my posts on DSL's. When you say DSL these
days, people think of Ruby-style internal DSL's, which are really API's
and not DSL's. True external DSL's have been almost impossible to
write, and folks have not been expecting that to change. So folks look
at my blog posts about Marpa DSL's and assume that I am talking about an
API, and not actual domain-specific *languages*.
Really. I have trained a dog to go to the store and buy his own biscuits.
-- jeffrey
On 03/23/2014 12:02 PM, Flavio Poletti wrote:
Oh I see! It was me to misread... sorry for that!
Ciao,
Flavio
Il 23/mar/2014 19:39 "Jeffrey Kegler" <[email protected]
<mailto:[email protected]>> ha scritto:
I'm not sure if I understood what you mean by "layout" correctly, but
{
company name => 'Kamamaya Technology', employee 1 => first name =>
'Jane', employee 1 => last name => 'Doe', employee 1 => title =>
'President', employee 2 => first name => 'John', employee 2 => last
name => 'Smith', employee 3 => first name => 'Clarence',
employee 3 =>
last name => 'Darrow',
}
where the layout is completely disarranged, parses exactly the
same as the original
{
company name => 'Kamamaya Technology',
employee 1 => first name => 'Jane',
employee 1 => last name => 'Doe',
employee 1 => title => 'President',
employee 2 => first name => 'John',
employee 2 => last name => 'Smith',
employee 3 => first name => 'Clarence',
employee 3 => last name => 'Darrow',
}
So in the sense of "arrangement of whitespace", the syntax is not
dependent on layout. (The above rearrangement was done by using
the Linux "fmt" command. Any other whitespace rearrangement will
work as well.)
I hope I'm reading your comment correctly. -- jeffrey
On 03/23/2014 11:04 AM, [email protected]
<mailto:[email protected]> wrote:
On Tuesday, March 11, 2014 7:09:46 PM UTC+1, Jeffrey Kegler wrote:
I have a new blog post
<http://jeffreykegler.github.io/Ocean-of-Awareness-blog/individual/2014/03/kv.html>
up: "Language design has been like shooting crap in a casino
that sets you up to win a lot of the first rolls before the
laws of probability grind you down."
It might be appealing at first sight, but its reliance on layout
makes it quite unperlish.
Ciao,
Flavio.
--
You received this message because you are subscribed to the
Google Groups "marpa parser" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in
the Google Groups "marpa parser" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/marpa-parser/C0415Qx_g18/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "marpa
parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
