Camm,
A quick update on this issue.
I have tried compiling with --enable-debug on my main machine, and
have tried both with and without --enable-debug on a second box.
Unfortunately, I cannot reproduce the failure under any of these
conditions.
I can work around the issue locally, and if this
Camm Maguire <[EMAIL PROTECTED]> writes:
> Greetings! This stuff sounds great, and likely can be included in the
> gcl distribution proper even though it is an ansi extension. I think
> slime depends on gray streams, right? That would be reason enough.
> But perhaps support should be in the for
Hi Waldek,
Waldek Hebisch <[EMAIL PROTECTED]> writes:
> Stephen Wilson wrote:
> > Stephen Wilson <[EMAIL PROTECTED]> writes:
> > > Could I suggest the following to replace these two cases:
> > >
> > > (+ 1 |negative| (round (log n 10)))
> >
> >
> > This should _not_ be used to replace both
Greetings! This stuff sounds great, and likely can be included in the
gcl distribution proper even though it is an ansi extension. I think
slime depends on gray streams, right? That would be reason enough.
But perhaps support should be in the form of an autoloadable module.
Take care,
Stephen
Greetings!
Just checking -- all that is of interest are the mpz functions, right?
(please see gmp docs if this does not make sense.)
Take care,
[EMAIL PROTECTED] writes:
> Camm,
>
> Can we reach the gmp functions explicitly in gcl?
> That is, can I do something like:
>
> (mpz_mod n d) ==> res
I have asked my student to try installing wh-sandbox, and to keep a
record of how he does it. If he's successful, I'll let you know. If
he's unsuccessful, I'll ask here again!
Thanks,
Alasdair
On 8/7/07, Bill Page <[EMAIL PROTECTED]> wrote:
> On 06 Aug 2007 13:02:50 -0500, Gabriel Dos Reis wrot
Greetings! Not yet, but I have been meaning to do this for some time,
and this may provide the needed impetus. It is really quite simple,
but cannot be achieved via the generic external shared library
interface described previously, due to the need to wrap the gmp
function calls to protect their
On 06 Aug 2007 13:02:50 -0500, Gabriel Dos Reis wrote:
> Bill Page writes:
>
> [...]
>
> | In the near future I will also be testing the build of FriCAS on Mac
> | OS X as part of the new version of axiom4sage.
>
> Bill --
>
> I've made some recent changes to build-improvements; please, could
> t
C Y <[EMAIL PROTECTED]> writes:
> Are they mutually exclusive?
In a sense, yes. Take a look at the Simple streams doc and see how
the traditional common lisp functions are redefined to support both
approaches. The starting point would probably be here:
http://www.franz.com/support/documentati
Gabriel Dos Reis wrote:
>
> It looks to me that the variable $LastCxArg in the routine
> /foobar from src/interp/spad.lisp is a type for |$LastCxArg|.
>
This rotine (and several others nearby) is probably junk.
It looks like debugging helper that got bitrotten and is
useless now.
--
Gabriel Dos Reis wrote:
>
> The global variable $SendXEventToHyperTeX is set twice:
>
> (1) once as a constant in sockio.lisp.pamphlet
>
>(defconstant |$SendXEventToHyperTeX| SendXEventToHyperTeX)
>
> (2) a second time in hypertex.boot.pamphlet
>
> SETANDFILEQ($SendXEventToHy
Stephen Wilson wrote:
> Stephen Wilson <[EMAIL PROTECTED]> writes:
> > Could I suggest the following to replace these two cases:
> >
> > (+ 1 |negative| (round (log n 10)))
>
>
> This should _not_ be used to replace both cases, but only the first.
> I believe the second case might be OK unle
On Mon, 6 Aug 2007, Waldek Hebisch wrote:
| > Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
| >
| > | When compiling with an ANSI common lisp compiler, the use of "sequence"
| > | in src/interp/parsing.lisp is resoled as referring to the standard symbol
| > | sequence, which belongs to locked stan
> Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
>
> | When compiling with an ANSI common lisp compiler, the use of "sequence"
> | in src/interp/parsing.lisp is resoled as referring to the standard symbol
> | sequence, which belongs to locked standard packages. I would suggest
> | to rename it to r
--- Stephen Wilson <[EMAIL PROTECTED]> wrote:
> I think they take different approaches, where both have advantages
> and disadvantages in certain applications. For example, I think
> Simple streams have a good interface for dealing with common byte-
> based operations like reading files, compress
C Y <[EMAIL PROTECTED]> writes:
> Not a particularly useful question, but I am curious - how serious is
> the collision conceptually between Gray Streams and Simple Streams? Is
> one a special case of the other, for example? (I.e. could Simple
> Streams be regarded as a special case layer on top
"Bill Page" <[EMAIL PROTECTED]> writes:
[...]
| In the near future I will also be testing the build of FriCAS on Mac
| OS X as part of the new version of axiom4sage.
Bill --
I've made some recent changes to build-improvements; please, could
try a build as of today and send me report?
Semes
On 8/6/07, Alasdair McAndrew wrote:
> There's instructions for building Axiom on Mac OS X at
>
> http://wiki.axiom-developer.org/BuildAxiom
>
> Are these instructions current? I have a student who would like to
> use Axiom on Mac OS X, and would prefer a native version, rather than
> a windows or
--- Stephen Wilson <[EMAIL PROTECTED]> wrote:
> I will start on getting some preliminary work done. Any more
> questions/thoughts would be greatly appreciated.
Not a particularly useful question, but I am curious - how serious is
the collision conceptually between Gray Streams and Simple Stream
C Y <[EMAIL PROTECTED]> writes:
> --- Stephen Wilson <[EMAIL PROTECTED]> wrote:
>
> > A large drawback is that neither, to my knowledge, have been
> > implemented atop GCL. I am seriously considering writing an
> > implementation. I have a personal preference for using Simple
> > Streams as I
Tim,
The following patch fixes the i-output issue. I figured the best
approach would be to write a utility function, digits-by-radix, which
allows one to determine the width of an integer given any radix. It
attempts to be reasonably efficient. I added this function to
vmlisp.lisp.pamphlet.
Tak
21 matches
Mail list logo
