[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Scripting language takes a silicon turn
- From: "mnewberry" <mnewberry@...>
- Date: Wed, 25 Jan 2006 18:06:56 -0700
Good point about {}. I hadn't thought about it in great detail.
But what's wrong with != and // ??
Michael
On Wed, 25 Jan 2006 16:47:56 -0800, Ben Sunshine-Hill wrote
> On 1/25/06, mnewberry <mnewberry@mirametrics.com> wrote:
> > I guess I don't see the problem with {} between the reserved keywords if,
> > else, and end becuase it would seem that the parser would always have a
> > context to work with.
>
> There isn't necessarily any context, because blocks aren't always
> introduced by if, while, etc. Take the code { a = 1 }. Table
> constructor or block?
>
> Ben
- References:
- Scripting language takes a silicon turn, Vijay Aswadhati
- Re: Scripting language takes a silicon turn, Brian Weed
- Re: Scripting language takes a silicon turn, Walter Cruz
- Re: Scripting language takes a silicon turn, Ben Sunshine-Hill
- Re: Scripting language takes a silicon turn, Walter Cruz
- Re: Scripting language takes a silicon turn, LEGO
- Re: Scripting language takes a silicon turn, Chris Marrin
- Re: Scripting language takes a silicon turn, Alen Ladavac
- Re: Scripting language takes a silicon turn, Chris Marrin
- Re: Scripting language takes a silicon turn, mnewberry
- Re: Scripting language takes a silicon turn, Ben Sunshine-Hill