• J Anderson (6/6) Dec 16 2003 The ada compiler would suggest a possible identifier that might be the
• The Lone Haranguer (2/8) Dec 16 2003
• Ilya Minkov (3/11) Dec 17 2003 I think that should be the job of the IDE. Especially IBM Eclipse users
• J Anderson (5/16) Dec 17 2003 I thought about that also, although it means that the IDE also has to
• J C Calvarese (10/19) Dec 18 2003 I doubt that Walter is going to add this to DMD anytime soon, but it may...
• J Anderson (2/21) Dec 18 2003 Cool
• Sean L. Palmer (12/31) Dec 19 2003 This is the reason why Walter is trying so hard to keep the parsing and
• Felix (2/36) Dec 19 2003
• Juan C. (5/39) Dec 19 2003 And therefore it ought to lead to removing much of the compile-time "saf...
• Sean L. Palmer (7/17) Dec 19 2003 True, Dlint would be pretty sophisticated. hehe

J Anderson <REMOVEanderson badmama.com.au> writes:

The ada compiler would suggest a possible identifier that might be the 
correct one when you misspelled a word.  Even a case check would be very 
useful. Could we please have that :)  It also means you don't have to 
know the case to use someone else class (just try the wrong one, and the 
compiler will give you alternatives).

-Anderson

The Lone Haranguer <The_member pathlink.com> writes:

Please! No more bloat!


In article <bro570$2vva$1 digitaldaemon.com>, J Anderson says...
The ada compiler would suggest a possible identifier that might be the 
correct one when you misspelled a word.  Even a case check would be very 
useful. Could we please have that :)  It also means you don't have to 
know the case to use someone else class (just try the wrong one, and the 
compiler will give you alternatives).

-Anderson

Ilya Minkov <minkov cs.tum.edu> writes:

I think that should be the job of the IDE. Especially IBM Eclipse users 
are used to this kind of service. ;)

J Anderson wrote:
 The ada compiler would suggest a possible identifier that might be the 
 correct one when you misspelled a word.  Even a case check would be very 
 useful. Could we please have that :)  It also means you don't have to 
 know the case to use someone else class (just try the wrong one, and the 
 compiler will give you alternatives).
 
 -Anderson
 

J Anderson <REMOVEanderson badmama.com.au> writes:

Ilya Minkov wrote:

 I think that should be the job of the IDE. Especially IBM Eclipse 
 users are used to this kind of service. ;)

I thought about that also, although it means that the IDE also has to 
phase the code.  It would be nice if D could spit out all of the 
identifiers into a text file (in categories). Although that'd mean 
another compiler switch, which Walter hates.

 J Anderson wrote:

 The ada compiler would suggest a possible identifier that might be 
 the correct one when you misspelled a word.  Even a case check would 
 be very useful. Could we please have that :)  It also means you don't 
 have to know the case to use someone else class (just try the wrong 
 one, and the compiler will give you alternatives).

 -Anderson

J C Calvarese <jcc7 cox.net> writes:

J Anderson wrote:
 Ilya Minkov wrote:
 
 I think that should be the job of the IDE. Especially IBM Eclipse 
 users are used to this kind of service. ;)

 I thought about that also, although it means that the IDE also has to 
 phase the code.  It would be nice if D could spit out all of the 
 identifiers into a text file (in categories). Although that'd mean 
 another compiler switch, which Walter hates.

I doubt that Walter is going to add this to DMD anytime soon, but it may 
not be that hard for one of us to create a tool just to parse the source 
to reach your goal.  Case in point:  I just added a feature to my 
version of D2HTML to output a raw list of identifiers in addition to an 
.html file.  They're unsorted, uncategorized, and redundant, but it's a 
start.

I thought you might be curious to see it in action: 
http://jcc_7.tripod.com/d/

Justin

J Anderson <REMOVEanderson badmama.com.au> writes:

J C Calvarese wrote:

 J Anderson wrote:

 Ilya Minkov wrote:

 I think that should be the job of the IDE. Especially IBM Eclipse 
 users are used to this kind of service. ;)

 I thought about that also, although it means that the IDE also has to 
 phase the code.  It would be nice if D could spit out all of the 
 identifiers into a text file (in categories). Although that'd mean 
 another compiler switch, which Walter hates.


 I doubt that Walter is going to add this to DMD anytime soon, but it 
 may not be that hard for one of us to create a tool just to parse the 
 source to reach your goal.  Case in point:  I just added a feature to 
 my version of D2HTML to output a raw list of identifiers in addition 
 to an ..html file.  They're unsorted, uncategorized, and redundant, 
 but it's a start.

 I thought you might be curious to see it in action: 
 http://jcc_7.tripod.com/d/

 Justin

Cool

"Sean L. Palmer" <palmer.sean verizon.net> writes:

This is the reason why Walter is trying so hard to keep the parsing and
semantic phases separate in D.  That will allow all kinds of tools to be
written that can deal with D source without having to know anything about
the types or the identifiers that are present.

In other words, it really won't be all that hard to write a tool that parses
D source.  You could probably do it in like 3 pages of Perl.  ;)   There
will probably be a Perl library for parsing D soon.

A full optimizing compiler, on the other hand, is a significant engineering
effort.  Some of those algorithms are pretty complicated!

Sean

"J C Calvarese" <jcc7 cox.net> wrote in message
news:bru2n8$2t1e$1 digitaldaemon.com...
 J Anderson wrote:
 Ilya Minkov wrote:

 I think that should be the job of the IDE. Especially IBM Eclipse
 users are used to this kind of service. ;)

 I thought about that also, although it means that the IDE also has to
 phase the code.  It would be nice if D could spit out all of the
 identifiers into a text file (in categories). Although that'd mean
 another compiler switch, which Walter hates.

 I doubt that Walter is going to add this to DMD anytime soon, but it may
 not be that hard for one of us to create a tool just to parse the source
 to reach your goal.  Case in point:  I just added a feature to my
 version of D2HTML to output a raw list of identifiers in addition to an
 .html file.  They're unsorted, uncategorized, and redundant, but it's a
 start.

 I thought you might be curious to see it in action:
 http://jcc_7.tripod.com/d/

 Justin

Felix <Felix_member pathlink.com> writes:

I agree with everything you say (and with Walter's conception, too).


In article <brubl2$9m0$1 digitaldaemon.com>, Sean L. Palmer says...
This is the reason why Walter is trying so hard to keep the parsing and
semantic phases separate in D.  That will allow all kinds of tools to be
written that can deal with D source without having to know anything about
the types or the identifiers that are present.

In other words, it really won't be all that hard to write a tool that parses
D source.  You could probably do it in like 3 pages of Perl.  ;)   There
will probably be a Perl library for parsing D soon.

A full optimizing compiler, on the other hand, is a significant engineering
effort.  Some of those algorithms are pretty complicated!

Sean

"J C Calvarese" <jcc7 cox.net> wrote in message
news:bru2n8$2t1e$1 digitaldaemon.com...
 J Anderson wrote:
 Ilya Minkov wrote:

 I think that should be the job of the IDE. Especially IBM Eclipse
 users are used to this kind of service. ;)

 I thought about that also, although it means that the IDE also has to
 phase the code.  It would be nice if D could spit out all of the
 identifiers into a text file (in categories). Although that'd mean
 another compiler switch, which Walter hates.

 I doubt that Walter is going to add this to DMD anytime soon, but it may
 not be that hard for one of us to create a tool just to parse the source
 to reach your goal.  Case in point:  I just added a feature to my
 version of D2HTML to output a raw list of identifiers in addition to an
 .html file.  They're unsorted, uncategorized, and redundant, but it's a
 start.

 I thought you might be curious to see it in action:
 http://jcc_7.tripod.com/d/

 Justin

Juan C. <Juan_member pathlink.com> writes:

And therefore it ought to lead to removing much of the compile-time "safety"
checks to other tools. I refer, of course, to flagging when a switch is missing
a default break, the  if ( x = y )  problem, etc. Then the compiler can focus on
compiling.

In article <brubl2$9m0$1 digitaldaemon.com>, Sean L. Palmer says...
This is the reason why Walter is trying so hard to keep the parsing and
semantic phases separate in D.  That will allow all kinds of tools to be
written that can deal with D source without having to know anything about
the types or the identifiers that are present.

In other words, it really won't be all that hard to write a tool that parses
D source.  You could probably do it in like 3 pages of Perl.  ;)   There
will probably be a Perl library for parsing D soon.

A full optimizing compiler, on the other hand, is a significant engineering
effort.  Some of those algorithms are pretty complicated!

Sean

"J C Calvarese" <jcc7 cox.net> wrote in message
news:bru2n8$2t1e$1 digitaldaemon.com...
 J Anderson wrote:
 Ilya Minkov wrote:

 I think that should be the job of the IDE. Especially IBM Eclipse
 users are used to this kind of service. ;)

 I thought about that also, although it means that the IDE also has to
 phase the code.  It would be nice if D could spit out all of the
 identifiers into a text file (in categories). Although that'd mean
 another compiler switch, which Walter hates.

 I doubt that Walter is going to add this to DMD anytime soon, but it may
 not be that hard for one of us to create a tool just to parse the source
 to reach your goal.  Case in point:  I just added a feature to my
 version of D2HTML to output a raw list of identifiers in addition to an
 .html file.  They're unsorted, uncategorized, and redundant, but it's a
 start.

 I thought you might be curious to see it in action:
 http://jcc_7.tripod.com/d/

 Justin

"Sean L. Palmer" <palmer.sean verizon.net> writes:

True, Dlint would be pretty sophisticated.  hehe

Sean

"Juan C." <Juan_member pathlink.com> wrote in message
news:brvcag$1r70$1 digitaldaemon.com...
 And therefore it ought to lead to removing much of the compile-time

"safety"
 checks to other tools. I refer, of course, to flagging when a switch is

missing
 a default break, the  if ( x = y )  problem, etc. Then the compiler can

focus on
 compiling.

 In article <brubl2$9m0$1 digitaldaemon.com>, Sean L. Palmer says...
This is the reason why Walter is trying so hard to keep the parsing and
semantic phases separate in D.  That will allow all kinds of tools to be
written that can deal with D source without having to know anything about
the types or the identifiers that are present.