>
> 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:
Ah, when I saw your suggested steps, I was hoping that your lazy/impatient
side had already won.
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.
I think #2 is a good compromise. I'll tentatively plan on taking that
approach. An argument for the lazy/impatient route is that existing code
can be changed to `select .type` today, and keep functioning as intended
(probably) on 1.10.0 and future releases. I'll start writing up a proposal,
and will send it to chapel-users and chapel-developers.
------------------------------------------------------------------------------
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
