From maintainers-request at octave dot org Wed Feb 22 14:05:54 2006 Subject: Re: Proposal for thread-safe interface to Octave internals From: "Sebastien Loisel" To: kraiskil at cc dot hut dot fi, "octave maintainers mailing list" Cc: "John Swensen" Date: Wed, 22 Feb 2006 21:04:18 +0100 ------=_Part_20238_21399377.1140638658316 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline John, Kalle, Just in case there are even more people interested in this, I'm forwarding to the list. S=E9bastien Loisel On 2/22/06, kraiskil at cc dot hut dot fi wrote: > > On Wed, 22 Feb 2006 08:34:32 -0700 John Swensen > wrote: > > > Kalle, > > I see you are going to help Sebastien with threading on the > > Workshop. > > Yes, Sebastien got a lot done in no-time, but there seems to be a few > things > I could still add :) I don't know how much time I can commit, tough. > > > I am going to try and > > get > > that whole class implemented this weekend. > > That would be great. > > > As someone mentioned earlier, "He who codes gets to > > choose". Regardless, I think we should use the same interface to the > > octave internals. > > Absolutely! I hope jwe accepts you patches: the API seemed very > reasonable. > If it got into Octave, there would of course not be any question about > using > anyhing else ;) > IIRC you code in C++ too? There could be more than just the Octave parts > that could be shared? > > > > > > Do you accept attachments in your email? I will email you the code > > once > > I have it complete. > > Sure. but I think I have a limit of 1MB. Could be old info, tough... > Which version of Octave will it be built on? > > I put Sebastien as a cc. > > Kalle > > P.S. The document you sent seems to need OOo2, could you please send a > copy in > pdf? I have still OOo1.x, haven't still read that part :( > ------=_Part_20238_21399377.1140638658316 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline John, Kalle,

Just in case there are even more people interested in t= his, I'm forwarding to the list.

S=E9bastien Loisel

On 2/22/06, kraiskil at cc dot hut dot fi <kraisk= il at cc dot hut dot fi> wrote:
On Wed, 22 Feb 2006 08:34:32 -0700 John Swensen <jswensen@intergate dot com> wrote:

> Kalle,=
>    I see you are going to help Sebastien with = threading on the
> Workshop.

Yes, Sebastien got a lot done in no-time, but there s= eems to be a few things
I could still add :) I don't know how much time = I can commit, tough.

>   I am going to try and
> = get
> that whole class implemented this weekend.

That would be great.=

>  As someone mentioned earlier, "He who codes ge= ts to
> choose".  Regardless, I think we should use th= e same interface to the
> octave internals.

Absolutely! I hope jwe accepts you patche= s: the API seemed very reasonable.
If it got into Octave, there would of= course not be any question about using
anyhing else ;)
IIRC you code= in C++ too? There could be more than just the Octave parts
that could be shared?


>
> Do you accept attachments= in your email?  I will email you the code
> once
> I= have it complete.

Sure. but I think I have a limit of 1MB. Could be= old info, tough...
Which version of Octave will it be built on?

I put Sebastien as = a cc.

Kalle

P.S. The document you sent seems to need OOo2, co= uld you please send a copy in
pdf? I have still OOo1.x, haven't still re= ad that part :(

------=_Part_20238_21399377.1140638658316--