[sage-support] Re: SAGE and .NET interoperability.

2010-01-17 Thread Dima Pasechnik
I need to correct myself again, as I made diff against an already "touched" file. :( Sorry for this mess. Here how it must be: 704a705 > static Obj ProtectFname; 723a725,726 > /* For some reason itanium GC seems unable to spot fname */ > ProtectFname = fname; 726a730,731 > ProtectFname = (Ob

[sage-support] Re: SAGE and .NET interoperability.

2010-01-11 Thread Dima Pasechnik
more precisely, the following (the original was putting the new global variable in the wrong place) 704a705 > static Obj ProtectFname; 727a729,731 > /* For some reason itanium GC seems unable to spot fname */ > ProtectFname = fname; > 730a735,736 > ProtectFname = (Obj)0L; > 1071a1078 > 1078a

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-11 Thread Dima Pasechnik
OK, this patch appears to fix the problem, indeed. Dima 2010/1/11 Stephen Linton : > Try this patch for saveload.c: > > 708a709 >> static Obj ProtectFname; > 727a729,731 >>   /* For some reason itanium GC seems unable to spot fname */ >>   ProtectFname = fname; >> > 730a735,736 >>   ProtectFname =

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-10 Thread William Stein
On Sun, Jan 10, 2010 at 1:06 PM, Stephen Linton wrote: > As far as I can tell, all the relevant code is identical in 4.4.10 + patch > and 4.4.12. Of course, I may (must, perhaps) have too narrow a definition of > relevant, but I wonder if its actually a matter of 4.4.10 being lucky in some > w

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-10 Thread William Stein
On Sun, Jan 10, 2010 at 10:17 AM, Dima Pasechnik wrote: > > On Jan 10, 11:56 pm, William Stein wrote: >> On Sat, Jan 9, 2010 at 11:10 PM, Dima Pasechnik wrote: >> > William, >> > I think I can reproduce one of your Itanium GAP bug; the workspace >> > filename gets mangled by SaveWorkspace. >> >

[sage-support] Re: SAGE and .NET interoperability.

2010-01-10 Thread Dima Pasechnik
On Jan 10, 11:56 pm, William Stein wrote: > On Sat, Jan 9, 2010 at 11:10 PM, Dima Pasechnik wrote: > > William, > > I think I can reproduce one of your Itanium GAP bug; the workspace > > filename gets mangled by SaveWorkspace. > > (so the workspace gets saved, but with a horribly wrong name...)

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-10 Thread William Stein
On Sat, Jan 9, 2010 at 11:10 PM, Dima Pasechnik wrote: > William, > I think I can reproduce one of your Itanium GAP bug; the workspace > filename gets mangled by SaveWorkspace. > (so the workspace gets saved, but with a horribly wrong name...) > Should be next to trivial to fix... > Dima Sweet.

[sage-support] Re: SAGE and .NET interoperability.

2010-01-09 Thread Dima Pasechnik
William, I think I can reproduce one of your Itanium GAP bug; the workspace filename gets mangled by SaveWorkspace. (so the workspace gets saved, but with a horribly wrong name...) Should be next to trivial to fix... Dima PS. Let's move this discussion over to sage-devel, as already suggested here

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-09 Thread William Stein
On Sat, Jan 9, 2010 at 11:36 AM, Dr. David Kirkby wrote: > Dima Pasechnik wrote: > >> William, >> I emailed you few weeks back asking what exactly you mean by Itanium >> environment, as I was unable to reproduce your problems on an Itanium >> cluster I have access to--- at least not with gcc. >> A

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-09 Thread Dr. David Kirkby
Dima Pasechnik wrote: William, I emailed you few weeks back asking what exactly you mean by Itanium environment, as I was unable to reproduce your problems on an Itanium cluster I have access to--- at least not with gcc. At least not in a stand-alone build of GAP. Intel compilers showed to be tr

[sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread Dima Pasechnik
> > By the way, anything new about moving to the newest GAP version? > > Somebody should post a new spkg.  Then I'll test it on Itanium and see > whether or not it works.  If not, then it doesn't go in, but we can at > least report the problem again to the GAP list. William, I emailed you few weeks

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread William Stein
On Fri, Jan 8, 2010 at 11:12 AM, Dima Pasechnik wrote: > > > On Jan 9, 12:17 am, William Stein wrote: >> On Fri, Jan 8, 2010 at 7:15 AM, Dag Sverre Seljebotn >> >> >> >> wrote: >> >> > Well Sage is a bit different than this because you'd want the full set >> >> > of tools for easy porting of SPK

[sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread Dima Pasechnik
On Jan 9, 12:17 am, William Stein wrote: > On Fri, Jan 8, 2010 at 7:15 AM, Dag Sverre Seljebotn > > > > wrote: > >> > Well Sage is a bit different than this because you'd want the full set > >> > of tools for easy porting of SPKGs -- bash, tar, make, gcc, ... > > >> well, that's if you want to

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread Robert Bradshaw
On Jan 8, 2010, at 10:10 AM, William Stein wrote: On Fri, Jan 8, 2010 at 9:58 AM, Robert Bradshaw wrote: For the record, this was already tried (using a combination of .bat files and standalone javascript). The problem is that even fewer people understood/were familiar with this build sys

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread William Stein
On Fri, Jan 8, 2010 at 9:58 AM, Robert Bradshaw wrote: > On Jan 8, 2010, at 7:02 AM, Dag Sverre Seljebotn wrote: > >> On Fri, 2010-01-08 at 06:51 -0800, dimpase wrote: >>> >>> On Jan 8, 9:59 pm, kcrisman wrote: > > no, it doesn't give you *any* reasonable figures, at all! > In fact, I

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread Robert Bradshaw
On Jan 8, 2010, at 7:02 AM, Dag Sverre Seljebotn wrote: On Fri, 2010-01-08 at 06:51 -0800, dimpase wrote: On Jan 8, 9:59 pm, kcrisman wrote: no, it doesn't give you *any* reasonable figures, at all! In fact, I am sure lots of people (a vast majority) are running Cygwin (or Mingw - a clone

[sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread kcrisman
> > Anyway, Dima, thanks for sorting my position that a Cygwin port of > Sage would be very valuable indeed! +1. All this time I assumed that Cygwin would require the same convolutions as the current VM or VirtualBox solution - which is fine for a heavy user, but probably not for someone who just

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread William Stein
On Fri, Jan 8, 2010 at 7:15 AM, Dag Sverre Seljebotn wrote: >> > Well Sage is a bit different than this because you'd want the full set >> > of tools for easy porting of SPKGs -- bash, tar, make, gcc, ... >> >> well, that's if you want to do Sage development, isn't it? >> (I'd be surprised if Sag

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread William Stein
On Fri, Jan 8, 2010 at 5:59 AM, kcrisman wrote: >> no, it doesn't give you *any* reasonable figures, at all! >> In fact, I am sure lots of people (a vast majority) are running Cygwin >> (or Mingw - a clone of Cygwin) apps on their Windows boxes without >> even realising this. Cygwin works quietly

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread Dag Sverre Seljebotn
On Fri, 2010-01-08 at 07:10 -0800, Dima Pasechnik wrote: > > On Jan 8, 11:02 pm, Dag Sverre Seljebotn > wrote: > > On Fri, 2010-01-08 at 06:51 -0800, dimpase wrote: > > > > > On Jan 8, 9:59 pm, kcrisman wrote: > > > > > no, it doesn't give you *any* reasonable figures, at all! > > > > > In fact,

[sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread Dima Pasechnik
On Jan 8, 11:02 pm, Dag Sverre Seljebotn wrote: > On Fri, 2010-01-08 at 06:51 -0800, dimpase wrote: > > > On Jan 8, 9:59 pm, kcrisman wrote: > > > > no, it doesn't give you *any* reasonable figures, at all! > > > > In fact, I am sure lots of people (a vast majority) are running Cygwin > > > > (

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread Dag Sverre Seljebotn
On Fri, 2010-01-08 at 06:51 -0800, dimpase wrote: > > On Jan 8, 9:59 pm, kcrisman wrote: > > > no, it doesn't give you *any* reasonable figures, at all! > > > In fact, I am sure lots of people (a vast majority) are running Cygwin > > > (or Mingw - a clone of Cygwin) apps on their Windows boxes wi

[sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread dimpase
On Jan 8, 10:40 pm, Kjetil Halvorsen wrote: > On Fri, Jan 8, 2010 at 10:59, kcrisman wrote: > >> no, it doesn't give you *any* reasonable figures, at all! > >> In fact, I am sure lots of people (a vast majority) are running Cygwin > >> (or Mingw - a clone of Cygwin) apps on their Windows boxes

[sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread dimpase
On Jan 8, 9:59 pm, kcrisman wrote: > > no, it doesn't give you *any* reasonable figures, at all! > > In fact, I am sure lots of people (a vast majority) are running Cygwin > > (or Mingw - a clone of Cygwin) apps on their Windows boxes without > > even realising this. Cygwin works quietly behind

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread Kjetil Halvorsen
On Fri, Jan 8, 2010 at 10:59, kcrisman wrote: >> no, it doesn't give you *any* reasonable figures, at all! >> In fact, I am sure lots of people (a vast majority) are running Cygwin >> (or Mingw - a clone of Cygwin) apps on their Windows boxes without >> even realising this. Cygwin works quietly be

[sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread kcrisman
> no, it doesn't give you *any* reasonable figures, at all! > In fact, I am sure lots of people (a vast majority) are running Cygwin > (or Mingw - a clone of Cygwin) apps on their Windows boxes without > even realising this. Cygwin works quietly behind the scenes here. > That is very interesting.

[sage-support] Re: SAGE and .NET interoperability.

2010-01-08 Thread dimpase
On Jan 7, 3:24 pm, Robert Bradshaw wrote: [...] > I'm more hopeful about the Sage Python classes--Python and Cython are   > both supported on Windows, and distutils is supposed to handle all the   > linking stuff. I'm not saying there won't be issues though--from what   > I've seen of it the path

[sage-support] Re: SAGE and .NET interoperability.

2010-01-07 Thread dimpase
On Jan 6, 10:49 am, David Kirkby wrote: > On Jan 3, 6:13 pm, Dima Pasechnik wrote: > > > Dave, > > it makes no sense to compare cygwin and virtualbox by Googlehits. > > Cygwin is just a tool to port Unix software to Windows quickly > > and relatively painlessly (at least the "command-line" softwa

Re: [sage-support] Re: SAGE and .NET interoperability.

2010-01-06 Thread Robert Bradshaw
Very interesting discussion--I'm glad to see stuff is still happening on this front, and great to hear from you again Blair. On Jan 5, 2010, at 6:49 PM, David Kirkby wrote: On Jan 3, 6:13 pm, Dima Pasechnik wrote: Also, note that many parts of Sage are not developed by Sage developers, e.g.

[sage-support] Re: SAGE and .NET interoperability.

2010-01-06 Thread David Kirkby
On Jan 3, 6:13 pm, Dima Pasechnik wrote: > Dave, > it makes no sense to compare cygwin and virtualbox by Googlehits. > Cygwin is just a tool to port Unix software to Windows quickly > and relatively painlessly (at least the "command-line" software > can usually be ported pretty quickly). Cygwin

[sage-support] Re: SAGE and .NET interoperability.

2010-01-02 Thread Harald Schilly
On Jan 2, 2:52 am, Jason Grout wrote: > Has andlinux (http://www.andlinux.org/) been relegated to the "been > there, tried that, didn't work very well" pile? I just wanted to bring up the same. http://www.colinux.org/ might have improved and how works the file system integation? Is it better than

[sage-support] Re: SAGE and .NET interoperability.

2010-01-01 Thread Jason Grout
Mike Hansen wrote: > On Fri, Jan 1, 2010 at 7:08 PM, Dr. David Kirkby > wrote: >> FWIW, a Google on Cywin brings up 4.8 million hits. On VirtualBox 4.2 million >> hits. Considering Cywin was released in 1995 and VirtualBox in 2007, it would >> suggest to me its a more popular tool today. > > Virt

[sage-support] Re: SAGE and .NET interoperability.

2009-12-31 Thread Jason Grout
dfg wrote: > Is this possible and, if yes, could you please explain how this can be > done or point me in the right direction? > Is it possible that you could use Sympy? Does Sympy run on IronPython, which presumably is easier to use from .NET? Thanks, Jason -- To post to this group, se