BTW - I hope you are not thinking that the special syntax makes it way
to the user. It does not.
On Wed, Feb 9, 2011 at 12:26 PM, Martin Logan wrote:
> On Wed, Feb 9, 2011 at 8:26 AM, Eric Merritt wrote:
>> I agree with you at the higher level. That exceptions need to be
>> distinguishable from
On Wed, Feb 9, 2011 at 8:26 AM, Eric Merritt wrote:
> I agree with you at the higher level. That exceptions need to be
> distinguishable from non-exception errors. I am not a big fan o this
> syntax though.
>
> In this we have two levels which are passing information back. The
> pmap level and the
I agree with you at the higher level. That exceptions need to be
distinguishable from non-exception errors. I am not a big fan o this
syntax though.
In this we have two levels which are passing information back. The
pmap level and the thing that is being pmapped. Both can return
values. However, I
One issue to think about is that the exception type becomes 'throw'
when done this way. I think that is an improvement over the current
behaviour but it would be nice if there was a throw/2.
On Tue, Feb 8, 2011 at 10:26 PM, Martin Logan wrote:
> Anyone else have a problem with this?
>
> On Tue, F
Anyone else have a problem with this?
On Tue, Feb 8, 2011 at 8:36 PM, Jordan Wilberding wrote:
> Go for it man.
> On Tue, Feb 8, 2011 at 9:26 PM, Martin Logan wrote:
>>
>> same with me, that is what I was going for, and what I have had to
>> replace pmap with for the time being because of the la
Go for it man.
On Tue, Feb 8, 2011 at 9:26 PM, Martin Logan wrote:
> same with me, that is what I was going for, and what I have had to
> replace pmap with for the time being because of the lack of this
> exception functionality. So if no one else objects then I am going to
> make the refactorin
same with me, that is what I was going for, and what I have had to
replace pmap with for the time being because of the lack of this
exception functionality. So if no one else objects then I am going to
make the refactoring which will be a major rev over the current api.
On Tue, Feb 8, 2011 at 8:19
I think we should emulate the behavior of regular map as much as possible.
JW
On Tue, Feb 8, 2011 at 9:12 PM, Martin Logan wrote:
> Guys, pmap needs to pass through exceptions. The implementation will
> be fairly straightforward, anyone against this?
>
> In the do_f function we have the line.
Guys, pmap needs to pass through exceptions. The implementation will
be fairly straightforward, anyone against this?
In the do_f function we have the line. I would change this line to
something like
Parent ! {self(), {error, ErrType, Error}}
Parent ! {self(), {'$exception$',
