Re: [fricas-devel] Intepreter: type declaration ignored in == AND:

2018-07-12 Thread Waldek Hebisch
> > As for "BOOT::|sayFunctionDeps| is undefined" error, it can be fixed > by following patch, > after the patch, ")display properties" works: > > (1) -> z == 2 >Type: Void > (2) -> )display properties z > Properties of z : >

Re: [fricas-devel] Intepreter: type declaration ignored in == AND: BOOT::|sayFunctionDeps| is undefined.

2018-07-11 Thread Bill Page
On Wed, Jul 11, 2018 at 9:53 AM, Riccardo GUIDA wrote: > > Hi, thanks for the feedback. > Actually, thank you for the feedback. > > [Bill]> Although this terminology is used in a few places, > > "... a few places"? Well, I would say "almost everywhere": > Jenks Sutor vol 0, hyperdoc, fricasUG,

Re: [fricas-devel] Intepreter: type declaration ignored in == AND: BOOT::|sayFunctionDeps| is undefined.

2018-07-11 Thread Riccardo GUIDA
Hi, thanks for the feedback. [Bill]> Although this terminology is used in a few places, "... a few places"? Well, I would say "almost everywhere": Jenks Sutor vol 0, hyperdoc, fricasUG, mathaction ... [Bill]>I do not think it [Bill]> is correct to call == delayed assignment. Rather it only

Re: [fricas-devel] Intepreter: type declaration ignored in == AND: BOOT::|sayFunctionDeps| is undefined.

2018-07-10 Thread oldk1331
> (2) -> y:Integer == 1 >Type: Void This is a strange way to input in FriCAS, it actually defined a rule for ':' (1) -> y:Integer == 1 Type: Void (2) ->

Re: [fricas-devel] Intepreter: type declaration ignored in == AND: BOOT::|sayFunctionDeps| is undefined.

2018-07-10 Thread Bill Page
On Tue, Jul 10, 2018 at 11:51 AM, Riccardo GUIDA wrote: > > Command line interpreter: I realize that type declaration is ignored > in delayed assignment == even for variables (see [1] for a similar > behavior for functions) > > Same behavior from .input file. > Although this terminology is used