I'm using Emacs 24.4 and Org-mode 8.2.10 (latest ELPA version), Ess 14.09, 
R 3.1.2 and I keep getting an ".ess.eval" error when using the session 
switch

A minimal example:
---------------------------
#+BEGIN_SRC R :exports both :session R
  mdot <- 28  #gal/min
#+END_SRC

#+BEGIN_SRC R :exports both :session R
  mdot
#+END_SRC

----------------------------

This get's sent to R but I get the following error in R:

Error: could not find function ".ess.eval"

After looking at the archives it looks like a fix may have been found, but 
I'm not sure that it made it back to 8.2.10.

Can some one please let me know if I'm using this wrong or if this is a 
bug in the system?


Thank you kindly,

--------------------------------------------------------------
Shawn Way, PE
MECO, Inc.
(p) 281-276-7612
(f)  281-313-0248

<a href="http://www.meco.com" target="_self"> 
   <img src="https://store.meco.com/awweb/img/meco_email.gif" alt="MECO" border="0"/> 
</a>
<br>
FIND US ON: <a href="https://www.youtube.com/user/MECOpure" target="_self"> <img src="http://mecoweb.com/images/youtube.jpg" alt="Youtube"  height="22" width="40" border="0"/>
<a href="https://www.linkedin.com/company/meco_2?trk=top_nav_home" target="_self"> <img src="http://mecoweb.com/images/linkedin.jpg" alt="Linkedin" height="22" width="22"  border="0"/> 
<a href="https://www.facebook.com/MecoWater" target="_self"> <img src="http://mecoweb.com/images/facebook.jpg" alt="Facebook"height="22" width="22" border="0"/> 
<a href="https://twitter.com/MECOpure" target="_self"> <img src="http://mecoweb.com/images/twitter.jpg" alt="Twitter" height="22" width="22" border="0"/> 
</a>
<br>
<br>
&nbsp;
    This e-mail is for the use of the intended recipient(s) only. If you have
    received this e-mail in error, please notify the sender immediately and then
    delete it. If you are not the intended recipient, you must not use, disclose 
    or distribute this e-mail without the author&#39;s prior permission. We have taken
    precautions to minimize the risk of transmitting software viruses, but we 
    advise you to carry out your own virus checks on any attachment to this message. We
    cannot accept liability for any loss or damage caused by software viruses.