• BCS <BCS_member pathlink.com> Mar 03 2006
• S. Chancellor <dnewsgr mephit.kicks-ass.org> Mar 05 2006
• John Demme <me teqdruid.com> Mar 05 2006

BCS <BCS_member pathlink.com> writes:

I'm looking for a list of things that are needed by 1.0

I'm not looking for a wish list, or a "things I would like" list. I'm talking 
about the "Walter should be sent to the nut house if he go's 1.0 without this"
list.

here's my start (add/remove at as you see fit):

the language it's self
--Implicit templates
--protection attributes (by general consensus(?) these can use some work.)
--any ambiguity that makes it imposable to find out it if code is valid(*)


the compiler
--all known major bugs (e.i. seg-v's on valid code, invalid code generation,
...)
--array ops

both
--sync DMD with the D spec, e.i. VERIFY that DMD is a fully compliant compiler
	(note: this will make sure that the spec is consistent and implantable)


(*) things like digitalmars.D.bugs/5671
BTW this bug is also in DMC

S. Chancellor <dnewsgr mephit.kicks-ass.org> writes:

On 2006-03-03 17:18:13 -0800, BCS <BCS_member pathlink.com> said:

 I'm looking for a list of things that are needed by 1.0
 
 I'm not looking for a wish list, or a "things I would like" list. I'm 
 talking about the "Walter should be sent to the nut house if he go's 
 1.0 without this" list.
 
 here's my start (add/remove at as you see fit):
 
 the language it's self
 --Implicit templates
 --protection attributes (by general consensus(?) these can use some work.)
 --any ambiguity that makes it imposable to find out it if code is valid(*)
 
 
 the compiler
 --all known major bugs (e.i. seg-v's on valid code, invalid code 
 generation, ...)
 --array ops
 
 both
 --sync DMD with the D spec, e.i. VERIFY that DMD is a fully compliant compiler
 	(note: this will make sure that the spec is consistent and implantable)
 
 
 (*) things like 
 digitalmars.D.bugs/5671
 BTW this bug is also in DMC


Anonymous arrays.

John Demme <me teqdruid.com> writes:

BCS wrote:
Full debugging information.

~John Demme


 I'm looking for a list of things that are needed by 1.0
 
 I'm not looking for a wish list, or a "things I would like" list. I'm
 talking about the "Walter should be sent to the nut house if he go's 1.0
 without this" list.
 
 here's my start (add/remove at as you see fit):
 
 the language it's self
 --Implicit templates
 --protection attributes (by general consensus(?) these can use some work.)
 --any ambiguity that makes it imposable to find out it if code is valid(*)
 
 
 the compiler
 --all known major bugs (e.i. seg-v's on valid code, invalid code
 generation, ...) --array ops
 
 both
 --sync DMD with the D spec, e.i. VERIFY that DMD is a fully compliant
 compiler (note: this will make sure that the spec is consistent and
 implantable)
 
 
 (*) things like
 digitalmars.D.bugs/5671 BTW
 this bug is also in DMC