Hi Brian, you probably don't get updates on pull requests to my repository, but you should be able to view the changes here [1] and comment on them.
To comment on the changes you can go to the "conversation" tab, and to see the actual changes to the files you can go to the "files changed" tab. Bill. [1] https://github.com/wbhart/mpir/pull/169 On 16 January 2016 at 15:11, Brian Gladman <b...@gladman.plus.com> wrote: > On 15/01/2016 20:01, Alex Dyachenko wrote: > > > At the time I started almost two years ago, there was a much simpler > > wrapper or two, searching now yields a couple, but they are both for > > integers only and don't use deferred execution. At any rate, there > > isn't one that's officially part of MPIR, so I thought I'd make one. > > > > Visual Studio does assume Windows; I haven't done any work in c# on > > Linux so that is indeed a very good question. Since my interop is > > written in C++/CLI, it's most likely a no-go for Linux, but according to > > http://tirania.org/blog/archive/2011/Dec-19.html Mono on Linux can > > already consume C++ directly so I'm guessing it can just use the native > > MPIR C++ interface. Mine was an effort to open MPIR to Windows .Net > > developers. > > > > On Linux, "makeinfo mpir.texi" runs without error, but "make pdf" gets > > me a "No rule to make target 'pdf'". However I can use "texi2dvi --pdf > > mpir.texi" to create a PDF; is that the same thing? > > > > I'm confused about diff vs. whole project. I was envisioning that my > > files, 95% of which are new and a handful existing MPIR files slightly > > modified, would become part of your repo just like Brian's VS builds now > > are. Then anyone downloading an MPIR release sources from mpir.org > > would have the option, if they like, to build my adapter and consume it. > > The other way this can work, and they can do it today, is if they clone > > my own fork, but I wonder if anyone in the world besides the readers of > > this thread knows about it. > > Can I assume that the changes you want in MPIR itself add extra calls > without changing the MPIR external interface as it is now. It would be > worth knowing a bit more about the changes you need here. > > Do you envisage the addition of another directory witin the MPIR > directory at the same level as the build.vc and build.vc<nn> > directories? That is something like mpir/build.net > > The way we are currently working is that Bill maintains the master MPIR > repository, whereas I maintain the Visual Studio build components as a > part of my own repository at https://github.com/BrianGladman/mpir > > When Bill is ready to make a new release he pulls from my repository as > a part of the process. I imagine he would do the same with your > repository once your additions become a part of MPIR. > > best regards, > > Brian > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mpir-devel+unsubscr...@googlegroups.com. > To post to this group, send email to mpir-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/mpir-devel. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at https://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
