Re: Explicitly unimplemented computed gotos

2010-11-26 Thread bearophile
Iain Buclaw: > I don't think this feature really warrants a new keyword. I have not asked for a new keyword. > Something that *would* warrant perhaps a new keyword would be non-local > gotos, but > it's usefulness is very negligible... I don't like those :-) Bye, bearophile

Re: Explicitly unimplemented computed gotos

2010-11-26 Thread Iain Buclaw
== Quote from bearophile (bearophileh...@lycos.com)'s article > When I have suggested to add "computed gotos" (similar to the ones of GCC) to > D, Walter has answered that they need some work to be implemented, and they have limited usefulness, almost only to optimize interpreters. > But: > - D is

Re: Explicitly unimplemented computed gotos

2010-11-25 Thread Adam D. Ruppe
bearophile wrote: > 1) Invent a syntax to represent and use them (probably the GCC syntax is good, because it's already known in C). I'd argue that we have a syntax reserved for them already: switch(x) { case 0: case 1: case 2: [..] } And this is just a little optimization in the ge

Re: Explicitly unimplemented computed gotos

2010-11-25 Thread Jimmy Cao
Good suggestion for a D3 feature. Wikipedia says this is also called an "Assigned Goto." It could make writing interpreters more efficient. On Thu, Nov 25, 2010 at 9:55 PM, bearophile wrote: > When I have suggested to add "computed gotos" (similar to the ones of GCC) > to D, Walter has answered t

Explicitly unimplemented computed gotos

2010-11-25 Thread bearophile
When I have suggested to add "computed gotos" (similar to the ones of GCC) to D, Walter has answered that they need some work to be implemented, and they have limited usefulness, almost only to optimize interpreters. But: - D is a system language, so writing interpreters is an important applicat