On Fri, 9 Aug 2002, Dan Sugalski wrote:
> At 10:00 AM +0200 8/9/02, Josef Hook wrote:
> >On Fri, 9 Aug 2002, Dan Sugalski wrote:
> >
> >> At 9:40 AM +0200 8/9/02, Josef Hook wrote:
> >> >I hate to bring this up again but i must. Dan what's the status on my
> >> >matrix patch ? I would apreciate some feedback if its good or bad?
> >> >If its going to be applied or not?
> >> >Do you want me to change anything?
> >>
> >> Sorry--you were going to redo this as a standalone PMC class, right?
> >> I'm pretty sure that was the plan.
> >
> >I thought you werent sure wether you wanted it in the core or not.
> >I guess i gave a hint that i could put everything in matrix.pmc but i
> >didnt got the message that i should (my fault). Anyway you want most of
> >the code in matrix.pmc ? no more matrix_core.c matrix_core.h?
> >Could i keep cell.c and cell.h in core as is ?
> >It would make it easier as i use them in multiarray.pmc
>
> Sorry, I probably wasn't clear. :(
>
> What I wanted originally was everything in a single file, as
> matrix.pmc. While I'm considering other things now, I'm not sure if
> that might not be because it's really late.
>
> If putting all the code into matrix.pmc is going to be a problem,
> this'd be the time for us to come up with a scheme for multi-file PMC
> classes. I'm not sure what, if anything, we'll do to facilitate
> code-sharing between PMC classes, but I don't think putting things
> into the core code is the right answer for that.
I agree this would mess up the core in the long run.
I just found a problem when putting everything in matrix.pmc i dont have
access to matrix struct and it in turn breaks all operations in matrix.ops
i guess i could figure out a workaround but as i see it i need to have
access to MATRIX struct. is there any suitable .h file where i could put
the struct in?
/j
> --
> Dan
>
> --------------------------------------"it's like this"-------------------
> Dan Sugalski even samurai
> [EMAIL PROTECTED] have teddy bears and even
> teddy bears get drunk
>
