Sean --

In my eagerness to see 'type select' go away, in formulating the proposed
plan, I forgot the potential need to retain 'type select' for a release
generating a warning in order to help transition users over in this step:

> * pull 'type select' from the parser and dead code eliminate anything
>  downstream from that that's possible (I'm guessing it's mostly in
>  the front end).

There are three possible approaches here:

1) retain existing behavior for 'type select' but have it generate a
    warning saying that it's going away and that users should rewrite
    to use 'select .type'

2) retain the parser's ability to see 'type select' but have it generate
    an error and pull out all downstream code.

3) just pull the whole thing.


Typically, we've done #1 or #2 when changing features and that's probably 
the high road to take.  The lazy/impatient part of me would be tempted to 
do #3, based on a sense that existing codes don't really use 'type select' 
much, which the bug regarding having two type selects in a single program 
would seem to suggest as well.  But it's rare that the lazy/impatient side 
of me is right.  So #2 might be the right mix of helping people along 
while also minimizing the amount of work required after the 1.11 release.

Or, if we propose the change on chapel-users, we could ask whether anyone 
actually uses 'type select' and if nobody replies, potentially use that as 
justification for #3 if we wanted my lazy/impatient side to win.

-Brad


------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers

Reply via email to