OK, I'm starting this thread mostly so people can post their progress
on getting the front end to a runnable state in linux.

On that note, I've started writing a billion little functions that
to get rid of all the undefined references to backend methods that
pop up when you build.
i.e.

// JON: stub function
struct elem * MulExp::toElem(IRState *irs)
{
     printf("MulExp::toElem() in expression.c\n");
}

Is this worthwhile do you think?

-Jon

STOP STOP STOP!!!
THIS IS ALL ALREADY DONE!!!
Jan



Jonathan Andrew wrote:

> OK, I'm starting this thread mostly so people can post their progress on getting the front end to a runnable state in linux.
>
> On that note, I've started writing a billion little functions that
> to get rid of all the undefined references to backend methods that
> pop up when you build.
> i.e.
>
> // JON: stub function
> struct elem * MulExp::toElem(IRState *irs)
> {
>       printf("MulExp::toElem() in expression.c\n");
> }
>
> Is this worthwhile do you think?
>
> -Jon

If you want to help, request CVS access so you can access the latest
sources!
Jan



Jonathan Andrew wrote:

> OK, I'm starting this thread mostly so people can post their progress on getting the front end to a runnable state in linux.
>
> On that note, I've started writing a billion little functions that
> to get rid of all the undefined references to backend methods that
> pop up when you build.
> i.e.
>
> // JON: stub function
> struct elem * MulExp::toElem(IRState *irs)
> {
>       printf("MulExp::toElem() in expression.c\n");
> }
>
> Is this worthwhile do you think?
>
> -Jon

OK, I just updated the .tar.gz. at http://www.opend.org/
Download it and you probably will find all these things already done.
I have tried to do it in such a way that I could leave the original code
as untouched as possible so that upgrading to a newer front-end would be
as easy as possible.
Please READ the messages in this newsgroup as I do update it frequently.
The last thing we want is double work as there is going to be enough work
to do.

Jan



Jonathan Andrew wrote:

> OK, I'm starting this thread mostly so people can post their progress on getting the front end to a runnable state in linux.
>
> On that note, I've started writing a billion little functions that
> to get rid of all the undefined references to backend methods that
> pop up when you build.
> i.e.
>
> // JON: stub function
> struct elem * MulExp::toElem(IRState *irs)
> {
>       printf("MulExp::toElem() in expression.c\n");
> }
>
> Is this worthwhile do you think?
>
> -Jon

Jan Knepper wrote:
> OK, I just updated the .tar.gz. at http://www.opend.org/
> Download it and you probably will find all these things already done.
> I have tried to do it in such a way that I could leave the original code
> as untouched as possible so that upgrading to a newer front-end would be
> as easy as possible.
> Please READ the messages in this newsgroup as I do update it frequently.
> The last thing we want is double work as there is going to be enough work
> to do.
> 
> Jan
> 

Hmm, could you put me on the CVS? I was a little wary before because I
felt I might break something, but now it seems like it will keep me
from duplicating anybody's work.

-Jon

You know how to use CVS?



Jonathan Andrew wrote:

> Jan Knepper wrote:
> > OK, I just updated the .tar.gz. at http://www.opend.org/
> > Download it and you probably will find all these things already done.
> > I have tried to do it in such a way that I could leave the original code
> > as untouched as possible so that upgrading to a newer front-end would be
> > as easy as possible.
> > Please READ the messages in this newsgroup as I do update it frequently.
> > The last thing we want is double work as there is going to be enough work
> > to do.
> >
> > Jan
> >
>
> Hmm, could you put me on the CVS? I was a little wary before because I felt I might break something, but now it seems like it will keep me from duplicating anybody's work.
>
> -Jon

Jan Knepper wrote:
> You know how to use CVS?
> 
> 

Frankly, no. :\

start here www.cvshome.org

If you're a windows type investigate wincvs, but I encourage you to learn the command line (it will facillitate knowledge)

Jonathan Andrew wrote:
> Jan Knepper wrote:
> 
>> You know how to use CVS?
>>
>>
> 
> Frankly, no. :\
> 
> 

andy wrote:
> start here www.cvshome.org
> 
> If you're a windows type investigate wincvs, but I encourage you to learn the command line (it will facillitate knowledge)
> 

Thanks, I'll have to read through this tonight.
-Jon

"andy" <acoliver@apache.org> wrote in message news:3D45F2BC.8070903@apache.org...

> >> You know how to use CVS?
> >
> > Frankly, no. :\
>
> start here www.cvshome.org
>
> If you're a windows type investigate wincvs, but I encourage you to learn the command line (it will facillitate knowledge)

   For Windows, I'd recommend TortoiseCVS over WinCVS. They use the same
core, IIRC, but Tortoise's interface is... awesome.

Salutaciones,
                         JCAB