bug-make
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: math expressions (was: Re: Tail call elimination)


From: Paul Smith
Subject: Re: math expressions (was: Re: Tail call elimination)
Date: Sun, 24 May 2020 19:11:47 -0400

On Sun, 2020-05-24 at 14:09 -0500, Pete Dietl wrote:
> > I think, as I mentioned before, that someone (I guess that's you
> > :)) should write up an actual proposal (maybe, for example, the
> > start of a new manual section) that can be examined and commented
> > on.
> 
> Challenge accepted! What is the best form to choose...
> maybe creating a branch of the source and adding a new manual page
> there that anyone can render?

As you may notice, Savannah doesn't support fork and pull request
capabilities like some other services, so we don't really have a way to
share branches like this.

You can just write the text and worry about formatting it later, or
make the changes to the texinfo file and send a diff, or make changes
to the texinfo file then format it for info output and send the
resulting formatted text.

As long as it's not a mess of unreadable HTML source it doesn't matter
to me :).

> > I do want to reiterate something I mentioned initially: any effort
> > of this size will require copyright assignment to the FSF / GNU
> > project.
> 
> Where can I find more information about this? And where do I do it?

I'll send you an email with next steps for this.

> > We can always use evaluation so you could just implement the basics
> > first and get grouping via evaluation for free, then add explicit
> > grouping as a next step if you want.
> 
> Yes incremental changes sound good. Would you recommend
> first trying to agree on a proposal and then attempt some
> implementation?
> Or to do these things together?

It's up to you.  If you want to just write something that's fine.  If
you feel like doing some prototyping would help you come up with the
proposal that's good too.  Note that we likely won't let amount of work
already completed to have much impact on requests to make changes, so
if it will cause sadness to throw out work or have to redo it, then the
less up-front work the better :).

FYI if you do start work on code be sure to read the GNU coding
standards which are slightly unique.  New code needs to follow the
existing formatting.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]