A similar discussion to this is going on in Facebook-land (no Facebook 
account should be required to read it, I believe):

        https://www.facebook.com/ChapelLanguage/posts/1761242420787583

The gist of it is me saying "This is morally not really different than 
permitting functions to have read/write access to module-scope variables" 
and Russel Winder saying "Yeah, you should get rid of that as well."

I'm not convinced the community would go for that change, but since it's 
come up, I guess it's worth asking...  Opinions?

-Brad


On Thu, 14 Jul 2016, Jason Riedy wrote:

> And Brad Chamberlain writes:
>> Please send any proposed keywords to me, optionally with a short
>> rationale.  In a few days, I'll send out a summary of responses received
>> (including our own brainstorming, which I don't want to influence you with
>> at the outset).
>
> Possibilities:
>  - hidden_state
>  - beware
>  - bugs_hide_here
>  - youll_regret_this
>  - later_developers_will_curse_your_name
>
> Are you sure this is needed?
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> Chapel-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/chapel-developers
>

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Chapel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-users

Reply via email to