RE : [mtasc] Strongly Typed Arrays in MTASC

[Bernard Poulin]

> But I think I can live with this hack, once a
> declaration like this is possible:

> var a : /*Number*/ Array = new /*Number*/Array();

I understand that this syntax can easily be "mixed" with normal comments (let's say the type was changed 'temporarily', leaving the previous type commented out next to it).
 
Here's a suggestion: What about using a special syntax inside the comment? That way it is less likely going to interfere with real comments. It might also hint a non-initiated developer that there might be something special hapenning here.  For example, we could prefix the type with # :
 
var a : /* #Number */ Array = new /* #Number */ Array();

or perhaps use the angle brackets (a bit like in C++ templates)?
 
var a : /*<Number>*/ Array = new /* <Number> */ Array();
 
Regards,
B.
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 3968 bytes
Desc: not available
Url : http://lists.motion-twin.com/pipermail/mtasc/attachments/20050917/ea71985a/attachment-0003.bin