> On May 26, 2019, at 9:15 PM, Ben Grasset wrote:
>
> Even if it doesn't happen right away, I 100% agree that this needs to be how
> they work eventually (which will not break Delphi compatibility, because how
> they work internally is irrelevant as long as the external means to access /
>
On Sat, May 18, 2019 at 2:57 PM Ryan Joseph
wrote:
> I wanted to make an alternate capture mode as an optimization for closures
> that don’t get passed outside of their scope but I wasn’t able to figure
> this out yet (using old-style objects instead of classes). It’s a waste to
> allocate a new
> On May 18, 2019, at 11:41 AM, Blaise Thorn wrote:
>
> Saturday, May 18, 2019 8:32 PM +03:00 from Ryan Joseph
> :
>> After 2 months now I’ve not been able to get the required sources to help
>> finish the closures branch.
>> The author Blaise did manage to contact me once but then went
Saturday, May 18, 2019 8:32 PM +03:00 from Ryan Joseph
:
> After 2 months now I’ve not been able to get the required sources to help
> finish the closures branch.
> The author Blaise did manage to contact me once but then went silent so I
> don’t know what happened.
Only yesterday, I have
After 2 months now I’ve not been able to get the required sources to help
finish the closures branch so I guess it’s best to go to plan B and see if it’s
feasible to finish at the last public repository I found. The author Blaise did
manage to contact me once but then went silent so I don’t
On Thu, Mar 21, 2019 at 4:40 PM Blaise Thorn wrote:
> Should you be interested in writing tests, I could give you the acess.
>
I'd also be very interested in assisting with this, now that I'm aware
you're willing to provide access to the repo.
___
Ryan Joseph schrieb am Do., 21. März 2019,
22:43:
>
>
> > On Mar 21, 2019, at 5:01 PM, Blaise Thorn wrote:
> >
> > Thursday, March 21, 2019 11:48 PM +03:00 from Ryan Joseph <
> r...@thealchemistguild.com>:
> >> Then maybe he’ll hear this and respond.
> >
> > I just did.
>
> Oh, you’re the
> On Mar 21, 2019, at 5:01 PM, Blaise Thorn wrote:
>
> Thursday, March 21, 2019 11:48 PM +03:00 from Ryan Joseph
> :
>> Then maybe he’ll hear this and respond.
>
> I just did.
Oh, you’re the author! I recognize the email now. Yes, please tell me what the
status is and what’s left to do. If
Thursday, March 21, 2019 11:48 PM +03:00 from Ryan Joseph
:
> Then maybe he’ll hear this and respond.
I just did.
> I’m happy to write tests
I will privately email you the details next week.
(FTR, since I asked for help with writing tests on this list, you are the
second one who volunteered
> On Mar 21, 2019, at 3:54 PM, Blaise Thorn wrote:
>
> FTR, the author automatically monitors this list for the keyword "closures”.
Then maybe he’ll hear this and respond. He’s been mentioned repeatedly over the
months and years but I have no idea if he’s still there or abandoned the
> do we even have contact with the author anymore?
FTR, the author automatically monitors this list for the keyword "closures".
> From what I can tell most the work is already done
IIRC, the last publicly available version lacks lifetime management support
amongst other crucial stuff.
FTR, the
So I came across a backup repo that Maciej made of the development for closures
(from 2015, not sure when the original author stopped working on it). I know
Sven said some months back the original author is still working on it but
that’s been said for literally years now and do we even have
On Thu, Jul 20, 2017 at 9:56 PM, Blaise Thorn wrote:
> There has been some feature-level progress; in particular, capturing across
> arbitrary level of nested and nameless routines is now supported, along with
> proper lifetime management.
>
> Sven has read-write access to the
There has been some feature-level progress; in particular, capturing across
arbitrary level of nested and nameless routines is now supported, along with
proper lifetime management.
Sven has read-write access to the source.
No other features are planned by me before the merge. I am currently
On 05.12.2016 15:12, bla...@blaise.ru wrote:
Otherwise, as I stated above, no help/answers is required for now; and
I am working.
What is the progress?
Ondrej
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
2016-12-05 17:46 GMT+01:00 :
>
> Because much communication occurred off-list.
:) in that case all is ok. Good luck. I have hope to see new release soon.
I will try to create few tests.
> if you do not have enough patience for FPC core team
>>
>
> What I do not have is
On 05.12.2016 17:57, Maciej Izak wrote:
the topic was almost dead for 1 year
Because much communication occurred off-list.
if you do not have enough patience for FPC core team
What I do not have is respect for schismatics who create unnecessary forks,
splitting the community and
2016-12-05 15:12 GMT+01:00 :
> 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
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.
In which, instead of accepting the offer, you chose to write a (much
appreciated) HOWTO.
(The offer stands; should you reconsider, kindly email me directly.)
Am 05.12.2016 14:37 schrieb :
>
> On 05.12.2016 13:36, Sven Barth wrote:
>
>> I didn't get any mail from Blaise during my holidays
>
>
> As agreed, I have allocated time, and I have been working.
> (FTR, I really want(ed) you to enlist for the task we discussed, so we
would work
On 05.12.2016 13:36, Sven Barth wrote:
I didn't get any mail from Blaise during my holidays
As agreed, I have allocated time, and I have been working.
(FTR, I really want(ed) you to enlist for the task we discussed, so we would
work in parallel.)
For now, with your latest letter, I have all
Am 05.12.2016 11:16 schrieb "Maciej Izak" :
>
>
> 2016-11-25 19:10 GMT+01:00 Sven Barth :
>>
>> Just to be sure: we're talking about the week from 28th to 2nd. If so,
yes I'll try to make sure that I'm available. Maybe I'll even hang around
on IRC
2016-11-25 19:10 GMT+01:00 Sven Barth :
> Just to be sure: we're talking about the week from 28th to 2nd. If so, yes
> I'll try to make sure that I'm available. Maybe I'll even hang around on
> IRC :)
Any new info? Link to repository? Should I continue?
--
Best
Am 25.11.2016 15:30 schrieb :
>
> On 24.11.2016 21:38, Sven Barth wrote:
>>
>> On 31.10.2016 14:58, bla...@blaise.ru wrote:
>>>
>>> I would like a commitment from at least one of the committers to work
closely with me during that period on resolving issues that prevent
merging.
> So what next? Blaise is still interested in? Am I alone on battle
> field? Is Scooter Software around? I am confused.
Yes, we're still around. Yes, we're still willing to throw some money
at anyone else who can help get this pushed in, whether that's Blaise,
Sven, or Maciej. I don't have
On 24.11.2016 21:38, Sven Barth wrote:
On 31.10.2016 14:58, bla...@blaise.ru wrote:
I would like a commitment from at least one of the committers to work closely
with me during that period on resolving issues that prevent merging. And by
that I mean to be ready to react to my
Am 25.11.2016 09:45 schrieb "Maciej Izak" :
>
>
> 2016-11-24 19:38 GMT+01:00 Sven Barth :
>>
>> mea culpa
>
>
> So what next? Blaise is still interested in? Am I alone on battle field?
Is Scooter Software around? I am confused.
Give them some time
2016-11-24 19:38 GMT+01:00 Sven Barth :
> mea culpa
So what next? Blaise is still interested in? Am I alone on battle field? Is
Scooter Software around? I am confused.
--
Best regards,
Maciej Izak
___
fpc-devel maillist
On 31.10.2016 14:58, bla...@blaise.ru wrote:
> On 31.10.2016 5:30, Zoë Peterson wrote:
>
>> We do need it in FPC proper though, not New Pascal
>
> I was going to ask you to clarify that; thanks.
>
>> Blaise, I'm fine settling up with you if Maciej takes over. Is there a
>> foreseeable schedule
We (Scooter Software) don't care who or how it it gets into Free Pascal,
as long as it eventually ends up there. :) We do need it in FPC proper
though, not New Pascal, because we need it on Linux and macOS, and our
build process is complicated enough that I wouldn't want to throw a
cross
2016-10-29 13:29 GMT+02:00 Florian Klämpfl :
> While I agree that we are merging invasive changes slowly, this is a
> little bit unfair as
> Generics.Collections required a lot of bugs to be fixed before it could be
> merged:
> http://bugs.freepascal.org/view.php?id=27206
Am 26.10.2016 um 00:58 schrieb Maciej Izak:
>
> to get important patches/modifications in reasonable time,
> for example merge for finished Generics.Collections took 2 years...
While I agree that we are merging invasive changes slowly, this is a little bit
unfair as
Generics.Collections
On Wed, 26 Oct 2016, Paul van Helden wrote:
Specially when they are as invasive as yours. You are in essence
converting pascal to a C++ clone with this MO patch. Is it so bad that this
is discussed thoroughly first ?
+1 for Oxygene mode. An Oxygene mode to me will be like early Christmas
On Wed, 26 Oct 2016, Maciej Izak wrote:
2016-10-26 11:56 GMT+02:00 Michael Van Canneyt :
As long as it's really a separate mode (plus maybe modeswitches for
selected features, that other modes might profit from) I don't see a
problem with adding an Oxygene mode.
On Wed, 26 Oct 2016, Sven Barth wrote:
Am 26.10.2016 00:58 schrieb "Maciej Izak" :
Many users likes more modern Pascal (for example oxygene mode is also one
of NewPascal targets), FPC core team likes more old fashioned Pascal... I
do not believe that core team would
Am 26.10.2016 00:58 schrieb "Maciej Izak" :
> Many users likes more modern Pascal (for example oxygene mode is also one
of NewPascal targets), FPC core team likes more old fashioned Pascal... I
do not believe that core team would accept oxygene mode/patch. Anyway...
As long as
2016-10-26 0:03 GMT+02:00 :
> Now you have me confused.
> I thought you wanted to "take over" acceptance of this into FPC and doing
> further improvements.
> What is this NewPascal? How official is it? Are the changes ported to FPC?
> (Googling through the lists.freepascal.org
On 26.10.2016 0:36, Maciej Izak wrote:
your work (with my modifications and with regression tests) will become part of
NewPascal release (for sure!) and I hope it makes you less frustrated :)
Now you have me confused.
I thought you wanted to "take over" acceptance of this into FPC and doing
2016-10-25 20:38 GMT+02:00 :
>
> 3) I have not abandoned this project (and I am as frustrated with the pace
> as you may be; although, the previous disruption was not my fault -- I had
> allocated last December to finally have this merged, but got no response
> from maintainers
On 25.10.2016 20:57, Maciej Izak wrote:
What Scooter Software has to GPL licensed code?
It has to do with what is right.
Allow me to provide a little background:
1) I do not use FPC at all;
2) Essentially, I was "hired" by Scooter Software (they do use FPC, I presume)
to implement the subj
2016-10-25 16:09 GMT+02:00 :
> In theory, that is fine by me (the author).
>
Good to hear that
> However, if I were to formally pass the bucket to you, I would like to
> settle with Scooter Software on my work done thus far.
>
What Scooter Software has to GPL licensed code?
2016-10-25 15:45 GMT+02:00 Michael Van Canneyt :
> One remark only: you should keep it independent of (or orthogonal to) the
> work you did on management operators. One should not depend on the other...
Yes I know and I agree :P One branch for Generics.Collections, one
On 25.10.2016 18:30, wkitt...@windstream.net wrote:
if i/we may ask, what happened to your Patch/hg repository? why did it go away?
As I said to Sven back then: "I did some server maintenance on 27th June, and I have
had no incentive to put that part back yet".
That is the only reason: lack
On 10/25/2016 10:09 AM, bla...@blaise.ru wrote:
On 25.10.2016 16:06, Maciej Izak wrote @
http://lists.freepascal.org/pipermail/fpc-devel/2016-October/037375.html :
I'd like to take over work on closures/anonymous methods
In theory, that is fine by me (the author).
However, if I were to
On 25.10.2016 16:06, Maciej Izak wrote @
http://lists.freepascal.org/pipermail/fpc-devel/2016-October/037375.html :
I'd like to take over work on closures/anonymous methods
In theory, that is fine by me (the author).
However, if I were to formally pass the bucket to you, I would like to
On Tue, 25 Oct 2016, Maciej Izak wrote:
Hi,
I'd like to take over work on closures/anonymous methods:
http://newpascal.org/compass.html (point #5).
Patch/hg repository from original author has gone away but I have made
copy. My working repository is here:
Hi,
I'd like to take over work on closures/anonymous methods:
http://newpascal.org/compass.html (point #5).
Patch/hg repository from original author has gone away but I have made
copy. My working repository is here:
https://github.com/maciej-izak/freepascal/commits/closures
I sent here
On 09.12.2015 11:43, bla...@blaise.ru wrote:
On 09.03.2015 16:36, bla...@blaise.ru wrote:
On 15.01.2012 18:26, Blaise wrote:
I have implemented the support for the Delphi-compatible non-generic
closures.
I am ready to commit the improved (and fully compilable) version.
Four years later,
Blaise wrote on Wed, 09 Dec 2015:
On 09.03.2015 16:36, bla...@blaise.ru wrote:
A) Things that work (at least, expected to -- before the merge):
* accessing outer variables/parameters/Selves from such routines
and from routines nested in them;
First of all, thanks for your work, and
On 09.03.2015 16:36, bla...@blaise.ru wrote:
On 15.01.2012 18:26, Blaise wrote:
I have implemented the support for the Delphi-compatible non-generic closures.
I am ready to commit the improved (and fully compilable) version.
Four years later, here comes (vastly improved) second attempt at a
On 09.12.2015 13:43, bla...@blaise.ru wrote:
http://hg.blaise.ru/public/fpc
Sorry, forgot:
In case someone wants to play, but does not want to clone & compile for himself
(and runs untrusted binaries), the executable for Windows/x86 is
http://blaise.ru/fpc/fpc-closures-9.7z . Should work
Great !
I am using a kind of home-brew pseudo closure (a function that ends with
"free;") in a project I am preparing.I'd be happy to use the formally
correct stuff.
-Michael
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
2015-12-09 11:43 GMT+01:00 :
> On 09.03.2015 16:36, bla...@blaise.ru wrote:
>
>> On 15.01.2012 18:26, Blaise wrote:
>>
>>> I have implemented the support for the Delphi-compatible non-generic
>>> closures.
>>>
>> I am ready to commit the improved (and fully compilable) version.
Am 09.03.2015 um 14:36 schrieb bla...@blaise.ru:
FPC trunk r30150, compiled with EXTDEBUG, emits a debug warning for
the following program:
--8--
type T = interface
procedure Bar;
end;
function Foo: T;
begin
result := nil
end;
begin
Foo().Bar()
// ^--
On 09 Mar 2015, at 14:36, bla...@blaise.ru wrote:
On 15.01.2012 18:26, Blaise Thorn wrote:
I have implemented the support for the Delphi-compatible non-
generic closures.
I am ready to commit the improved (and fully compilable) version.
Per Jonas Maebe's suggestion, I am going to create a
On 10.03.2015 15:47, Jonas Maebe wrote:
Do you already have an svn account?
The one I had back in 2012.
My old branch is here:
http://svn.freepascal.org/svn/fpc/branches/blaise/closures
It indicates a problem in the compiler.
Thanks.
Shall I file it in the bug tracker, then?
As the
On 10 Mar 2015, at 14:29, bla...@blaise.ru wrote:
On 10.03.2015 15:47, Jonas Maebe wrote:
Do you already have an svn account?
The one I had back in 2012.
My old branch is here:
http://svn.freepascal.org/svn/fpc/branches/blaise/closures
You should still have access to everything under
On 10.03.2015 15:09, Hans-Peter Diettrich wrote:
I'd assume that the warning refers to result := nil in Foo().
Wrong. And the comment clearly indicates to which line it refers.
This happens because of the call chaining.
--
βþ
___
fpc-devel maillist
On 15.01.2012 18:26, Blaise Thorn wrote:
I have implemented the support for the Delphi-compatible non-generic closures.
I am ready to commit the improved (and fully compilable) version.
Per Jonas Maebe's suggestion, I am going to create a new branch (also, last time I tried
to commit into
On 07.06.2013 18:44, Vasiliy Kevroletin wrote:
It's not yet available in trunk, just a work in progress. Though I DO
hope that it will be part of trunk once Vasiliy is finished :)
Regards,
Sven
I also hope that my work will be in trunk in the future. But instead of
big merge of separate
It's not yet available in trunk, just a work in progress. Though I DO
hope that it will be part of trunk once Vasiliy is finished :)
Regards,
Sven
I also hope that my work will be in trunk in the future. But instead of
big merge of separate brunch I would prefer to produce series of small
Am 27.05.2013 02:31 schrieb Paul Ishenin i...@kmiac.ru:
27.05.2013 5:52, Maciej Izak пишет:
So I am waiting impatiently ^^. I think it's interesting time for
FPC! To be completely happy, there is only one seriously lack - extended
RTTI. :)
RTTI has been extended recently:
27.05.2013 15:32, Sven Barth пишет:
The new extended RTTI introduced in Delphi 2009 which allows access to
private/protected/public members as well together with attributes and
things like TVirtualMethodInterceptor, Invoke and TValue.
Sven, I did not ask what and how delphi implemented. I
Sven, I did not ask what and how delphi implemented. I asked Maciej Izak
what he wants from extended RTTI. Maybe this is a small subset which is not
very hard to implement.
Best regards,
Paul Ishenin
Unfortunately, Sven is right :). I need this to share another free library
for FPC. It was
27.05.2013 17:17, Maciej Izak wrote:
Unfortunately, Sven is right :). I need this to share another free
library for FPC. It was originally intended for sale to the Embarcadero.
Absolute automatic binary streaming (seriously, for each type that
exists in Pascal, including Class, ClassRef,
If you don't need RTTI unit then it will be much more simplier to
implement your requirements.
Attributes are half ready in a branch. RTTI for non-published elements
(together with $RTTI directive) is not a very hard task.
I use a lot of TypInfo. If I get RTTI for non-published elements and
Vasiliy Kevroletin schrieb:
I described details of proposed and partly implemented approach in
mantis. This is Delphi's approach. Some people call it closures via
interfaces. In slightly modified way it will allow to capture variables
by value (which was requested in previous discussion). I
Am 27.05.2013 16:18 schrieb Hans-Peter Diettrich drdiettri...@aol.com:
Vasiliy Kevroletin schrieb:
I described details of proposed and partly implemented approach in
mantis. This is Delphi's approach. Some people call it closures via
interfaces. In slightly modified way it will allow to
Hi all,
About 2 months ago there was a big discussion about closures(thread
Delphi anonymous methods). After this discussion I started work on
Delhi-like closures for fpc. I am far from finish and current
implementation is not perfect. But I already have positive results: it's
possible to
On 26.05.2013 12:12, Vasiliy Kevroletin wrote:
Hi all,
About 2 months ago there was a big discussion about closures(thread
Delphi anonymous methods). After this discussion I started work on
Delhi-like closures for fpc. I am far from finish and current
implementation is not perfect. But I
On 26.05.2013 16:05, Sven Barth wrote:
On 26.05.2013 12:12, Vasiliy Kevroletin wrote:
Hi all,
About 2 months ago there was a big discussion about closures(thread
Delphi anonymous methods). After this discussion I started work on
Delhi-like closures for fpc. I am far from finish and current
Cool! Now I can fully complete library Generics.Collections for FPC
(especially Generics.Defaults) ;D (
https://code.google.com/p/fpc-generics-collections/ ).
FPC is getting stronger!
Regards,
HNB
___
fpc-devel maillist -
On 26.05.2013 21:16, Maciej Izak wrote:
Cool! Now I can fully complete library Generics.Collections for FPC
(especially Generics.Defaults) ;D (
https://code.google.com/p/fpc-generics-collections/ ).
It's not yet available in trunk, just a work in progress. Though I DO
hope that it will be
It's not yet available in trunk, just a work in progress. Though I DO hope
that it will be part of trunk once Vasiliy is finished :)
So I am waiting impatiently ^^. I think it's interesting time for FPC! To
be completely happy, there is only one seriously lack - extended RTTI. :)
Regards,
HNB
27.05.2013 5:52, Maciej Izak пишет:
So I am waiting impatiently ^^. I think it's interesting time for
FPC! To be completely happy, there is only one seriously lack - extended
RTTI. :)
RTTI has been extended recently:
http://wiki.lazarus.freepascal.org/User_Changes_Trunk#RTTI_changes
Please
: [fpc-devel] Closures via interfaces
27.05.2013 5:52, Maciej Izak пишет:
So I am waiting impatiently ^^. I think it's interesting time for
FPC! To be completely happy, there is only one seriously lack -
extended
RTTI. :)
RTTI has been extended recently:
http://wiki.lazarus.freepascal.org
Am 15.01.2012 16:27 schrieb Blaise Thorn m...@blaise.ru:
Hello.
I have implemented the support for the Delphi-compatible non-generic
closures.
Gradually, I plan to extend that support with:
* generic closures (I am not sure, though, how much current generics are
expected to be compatible
On 16.01.2012 16:05, Sven Barth wrote:
How firm are you with the implementation of generics inside the compiler?
Totally blank. Since you are the person who has been working on that area most
recently, I would actually appreciate if you could compile a document (on the
wiki?) outlining the
On 16.01.2012 15:11, Blaise Thorn wrote:
On 16.01.2012 16:05, Sven Barth wrote:
How firm are you with the implementation of generics inside the compiler?
Totally blank. Since you are the person who has been working on that
area most recently, I would actually appreciate if you could compile
Hello.
I have implemented the support for the Delphi-compatible non-generic closures.
Gradually, I plan to extend that support with:
* generic closures (I am not sure, though, how much current generics are
expected to be compatible with Delphi);
* Delphi-incompatible extensions (simple
Am 15.01.2012 16:26, schrieb Blaise Thorn:
My question is: how the work should be organised? Should a separate SVN
branch be created for this?
The best is to create an svn branch. See private mail.
___
fpc-devel maillist -
On Sun, Jan 15, 2012 at 17:38, Florian Klämpfl flor...@freepascal.orgwrote:
Am 15.01.2012 16:26, schrieb Blaise Thorn:
My question is: how the work should be organised? Should a separate SVN
branch be created for this?
The best is to create an svn branch. See private mail.
The best way
Am 15.01.2012 16:45, schrieb ik:
On Sun, Jan 15, 2012 at 17:38, Florian Klämpfl flor...@freepascal.org
mailto:flor...@freepascal.org wrote:
Am 15.01.2012 16:26, schrieb Blaise Thorn:
My question is: how the work should be organised? Should a
separate SVN
branch be created
On 15.01.2012 16:56, Florian Klämpfl wrote:
Am 15.01.2012 16:45, schrieb ik:
On Sun, Jan 15, 2012 at 17:38, Florian Klämpflflor...@freepascal.org
mailto:flor...@freepascal.org wrote:
Am 15.01.2012 16:26, schrieb Blaise Thorn:
My question is: how the work should be organised?
In our previous episode, Sven Barth said:
repository allows everybody to review it what e.g. I try to do with
every commit to the central fpc svn repository.
Well... at least for me the use of Git (together with Git-SVN) provided
the possibility for me to commit code while on the train (I
85 matches
Mail list logo