On Tue, Feb 21, 2017 at 11:46 PM, Waldek Hebisch
wrote:
> However, there
> are now various cheap and relatively small ARM board.
> Autolading may help them.
Hmm, did anyone run FriCAS on ARM before? Since
FriCAS doesn't support cross compile, building it natively
on
Any update? This is definitely an improvement to current
situation, with no drawbacks.
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Why not? I think this is useful for debugging and currently
not in the system.
On Wed, Feb 22, 2017 at 12:11 AM, Waldek Hebisch
wrote:
> oldk1331 wrote:
>>
>> On Mon, Feb 20, 2017 at 9:45 PM, Waldek Hebisch
>> wrote:
>> > I am also using
> I think we should remove all CCF with CFLAGS, opinions?
I revise this a little: we treat CCF as default c flags, but we should
also honor CFLAGS. ($(CC) $(CCF) $(CFLAGS))
On Tue, Feb 21, 2017 at 11:20 PM, Waldek Hebisch
wrote:
> I think this is case when old saying
On 02/21/2017 04:46 PM, Waldek Hebisch wrote:
> oldk1331 wrote:
>>
>> "autoload" is gone in the last release, and
>> "share/texmf/tex" is not used, so no need to install
>> empty directories.
>
> When I disabled autoloading of parts of interpreter I did only
> minimal change, so to anybody who
About a year ago I did just what RJF is suggesting by using* embeddable
Maxima *(https://github.com/nilqed/embeddable-maxima) via QuickLisp and a
simple interface
(https://github.com/nilqed/fricas_input/tree/master/spad/maxima) inspired
by RJF's Mockmma (actually I reused a lot of code from
>
> Is it OK to commit this patch?
Commited.
> > Have you compared current code with HyperDoc?
>
> HyperDoc can only handle fully specified type (not type constructor),
> eg. FRAC INT is OK while FRAC isn't. Correct?
Not correct. FRAC works fine in HyperDoc. Only to get
info about
oldk1331 wrote:
>> I'm not familiar with SAGE, but I assume interoperability of SAGE
>> is based on string and parsing? And FriCAS is not a "first class ciziten"
>> of SAGE?
>
> 'Martin R' wrote:
> both of these assertions are currently true. apparently, there is not
> enough interest in using
oldk1331 wrote:
>
> On Mon, Feb 20, 2017 at 9:45 PM, Waldek Hebisch
> wrote:
> > I am also using helper packages in similar situation.
> > However:
> > - to get S-expression corresponding to type use 'devaluate'
> > - there is coercion of types to OutputForm, use it
oldk1331 wrote:
>
> "autoload" is gone in the last release, and
> "share/texmf/tex" is not used, so no need to install
> empty directories.
When I disabled autoloading of parts of interpreter I did only
minimal change, so to anybody who wants it can restore it
easily. If we decide that we never
oldk1331 wrote:
>
> "./configure -h" mentions CFLAGS, but CFLAGS is not
> used in src/lib/Makefile.in, while CCF is used in may
> places.
>
> I think we should remove all CCF with CFLAGS, opinions?
I think this is case when old saying "do not fix what is
not broken" applies. 'CFLAGS' in
In ")show FloatingPointSystem", there is:
max : () -> % if not(has($,arbitraryPrecision)) and
not(has($,arbitraryExponent))
I did a simple grep, I think FloatingPointSystem is the only
place that "not" appeared in the Exports part.
In the code, "not" is represented by |not|, so the lower case
"./configure -h" mentions CFLAGS, but CFLAGS is not
used in src/lib/Makefile.in, while CCF is used in may
places.
I think we should remove all CCF with CFLAGS, opinions?
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To
>
> I'm not familiar with SAGE, but I assume interoperability of SAGE
> is based on string and parsing? And FriCAS is not a "first class ciziten"
> of SAGE?
both of these assertions are currently true. apparently, there is not
enough interest in using fricas from sage. although i
14 matches
Mail list logo