Services & Resources / Wolfram Forums / MathGroup Archive
-----

MathGroup Archive 2013

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: inconsistent refinement behavior

  • To: mathgroup at smc.vnet.net
  • Subject: [mg131370] Re: inconsistent refinement behavior
  • From: Bill Rowe <readnews at sbcglobal.net>
  • Date: Sun, 14 Jul 2013 01:48:06 -0400 (EDT)
  • Delivered-to: l-mathgroup@mail-archive0.wolfram.com
  • Delivered-to: l-mathgroup@wolfram.com
  • Delivered-to: mathgroup-outx@smc.vnet.net
  • Delivered-to: mathgroup-newsendx@smc.vnet.net

On 7/12/13 at 2:49 AM, akrasnov at cory.eecs.berkeley.edu (Alex Krasnov)
wrote:

>Firstly, x==0 also implicitly assumes that x is in Reals, since 0 is
>in Reals, as the following examples demonstrate:

>In:    Assuming[x==0, Refine[Element[x, Reals]]] Out:  True

>In:    Assuming[{Element[x, Reals], x==0}, Refine[Infinity/x]]
>Out:   ComplexInfinity

No so. Consider

In[1]:= Assuming[x == 0, Refine[Element[x, Complexes]]]

Out[1]= True




  • Prev by Date: Re: inconsistent refinement behavior
  • Next by Date: Re: What is the actual simulation time of NDSolve?
  • Previous by thread: Re: inconsistent refinement behavior
  • Next by thread: Re: inconsistent refinement behavior