Actually the message "Semantic Errors" occurs 35 times during a normal
successful build of FriCAS. Many but not all of these are due to
something being "BOTH a variable and a literal". Clearly these are not
really "errors". At most this might be just a helpful warning but I
cannot see any situation in SPAD where treating something as both a
variable and a literal. In fact it is not really clear what might be
meant by this message.

According to the build log there are 56 instances of using a symbol as
both a variable and a literal:

 algebraicGcd2:  pss1 is BOTH a variable and a literal
 algebraicGcd3a:  pss1 is BOTH a variable and a literal
 coerce:  arrows is BOTH a variable and a literal
 common:  contents is BOTH a variable and a literal
 common:  name is BOTH a variable and a literal
 createSceneArrow:  en is BOTH a variable and a literal
 createSceneArrow:  mode is BOTH a variable and a literal
 createSceneArrow:  offset is BOTH a variable and a literal
 createSceneArrow:  size is BOTH a variable and a literal
 createSceneArrows:  mode is BOTH a variable and a literal
 createSceneArrows:  size is BOTH a variable and a literal
 createSceneArrow:  st is BOTH a variable and a literal
 createSceneLine:  en is BOTH a variable and a literal
 createSceneLine:  st is BOTH a variable and a literal
 createSceneNamedPoints:  np is BOTH a variable and a literal
 ddfact:  degree is BOTH a variable and a literal
 ddFact:  degree is BOTH a variable and a literal
 ddfactor:  degree is BOTH a variable and a literal
 do_poly_integer0:  pss1 is BOTH a variable and a literal
 eval:  a is BOTH a variable and a literal
 eval_and_solve:  pss1 is BOTH a variable and a literal
 eval:  b is BOTH a variable and a literal
 eval:  c is BOTH a variable and a literal
 eval:  d is BOTH a variable and a literal
 factorUP:  x is BOTH a variable and a literal
 factor:  x is BOTH a variable and a literal
 factor:  y is BOTH a variable and a literal
 finitePoset:  struct1 is BOTH a variable and a literal
 FloatingPointSystem: struct1 is BOTH a variable and a literal
 forLoop:  body is BOTH a variable and a literal
 gen_exp:  x is BOTH a variable and a literal
 gen_exp:  y is BOTH a variable and a literal
 HANKP: rels is BOTH a variable and a literal
 inferFromRelations:  rels is BOTH a variable and a literal
 jacobi2polypq :  a is BOTH a variable and a literal
 jacobi2polypq :  b is BOTH a variable and a literal
 jacobi2polypq : c is BOTH a variable and a literal
 jacobi2polypq : d is BOTH a variable and a literal
 lift_rightfactor:  x is BOTH a variable and a literal
 listream_coefsop:  x is BOTH a variable and a literal
 monomials1:  c is BOTH a variable and a literal
 monomials1:  k is BOTH a variable and a literal
 mul is BOTH a variable and a literal
 orientedFacet:  mul is BOTH a variable and a literal
 proportional?:  a is BOTH a variable and a literal
 proportional?:  b is BOTH a variable and a literal
 proportional?:  c is BOTH a variable and a literal
 proportional?:  d is BOTH a variable and a literal
 ramification_of:  x is BOTH a variable and a literal
 reducedSystem:  vec is BOTH a variable and a literal
 relatorTables:  rels is BOTH a variable and a literal
 separateFactors:  degree is BOTH a variable and a literal
 sepFact1:  degree is BOTH a variable and a literal
 sepfact:  degree is BOTH a variable and a literal
 validate:  last is BOTH a variable and a literal
 xmlAttribute:  value is BOTH a variable and a literal

--

These function names before the : above are not so useful but it would
have been a bit difficult to extract actual file names from the grep.
Anyway, the point is that if these really are not errors, then the
compiler should not flag them as such.

-- 
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 fricas-devel+unsubscr...@googlegroups.com.
To post to this group, send email to fricas-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to