[fpc-devel] Closures / anonymous methods
hnb.code at gmail.com
Mon Dec 5 15:57:37 CET 2016
2016-12-05 15:12 GMT+01:00 <Blaise at blaise.ru>:
> On 05.12.2016 16:44, Sven Barth wrote:
> You mean that from around a year ago?
> No. Your latest letter to me is dated 26.11.2016.
I see big problem with communication. Seems like I am special mediator.
Without my notification the topic was almost dead for 1 year. Now we have
similar situation again probably for another year or two.
I need that feature to start many other related features in my compiler
work. For example I like to start experiments with "yield" and other stuff
(compiler code behind closures is usefully).
>From my experience with management operators:
* The patch can't be simple as one big patch, the working feature is just a
start (in current form, closures are not in that stage yet - see problems
with already implemented "blocks" by Jonas). State of closures IMO is far
far away from "ready to merge".
* When big patch is ready you need to rework whole patch for small commits
* Each owner/author of feature, should be able to create full-test suite,
generally only author knew how it works in all details, and how to create
proper test suite to cover low level scenarios, so community could not help
much with test suite (sure - bug reports and related tests are fine but I
mean test suite prepared by core team for each new feature).
* The style of compiler code *must* be exactly same in all parts (after
many hours with compiler I think it is perfect).
Did I miss something important? I might be wrong.
Let me know if you do not have enough patience for FPC core team ;). I will
do it :P...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fpc-devel