<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>What are the VBScript reference semantics for object members?</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx</link><description>Basically, the rule is pretty simple -- if you want to pass a variable by reference, you've got to pass the variable, period. VBScript does not support passing object properties by reference.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>RE: What are the VBScript reference semantics for object members?</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx#53007</link><pubDate>Tue, 16 Sep 2003 04:49:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:53007</guid><dc:creator>Matthew</dc:creator><description>You state:

A: Probably for backwards compatibility with VB5, 4, 3, 2 and 1, which incidentally was called &amp;quot;Object Basic&amp;quot;.  Ah, the halcyon days of my youth. 

I think from memory if you have a public member variable in an earlier version of VB (maybe VB 4?) it does actually let you pass it Byref. It was changed in later versions (I can't find the actual MS article discussing it though).</description></item><item><title>RE: What are the VBScript reference semantics for object members?</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx#53008</link><pubDate>Tue, 16 Sep 2003 05:10:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:53008</guid><dc:creator>Eric Lippert</dc:creator><description>You may well be right.  Like I said, it was years and years ago that this decision was made, and I wasn't exactly heavily consulted at the time.  If you happen to find a reference, I'd be amused to see it.  Or, perhaps in my copious spare time I'll look through the VBA source code logs -- I have them around here somewhere...</description></item><item><title>RE: What are the VBScript reference semantics for object members?</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx#53009</link><pubDate>Wed, 17 Sep 2003 01:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:53009</guid><dc:creator>Blake</dc:creator><description>VB 1 wasn't called Object Basic the way I remember it.   That was just called Thunder.  I'm pretty sure the Object Basic moniker came when VB 2 was in the works.  There were to be several flavors, Ruby, Silver and something, which eventually became VB, VBA &amp;amp; VBScript.

Or am I just getting senile?</description></item><item><title>RE: What are the VBScript reference semantics for object members?</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx#53010</link><pubDate>Wed, 17 Sep 2003 01:31:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:53010</guid><dc:creator>Eric Lippert</dc:creator><description>I don't recall if Object Basic was VB1 or VB2 -- that was before my time, as I did not start interning on the VB team until VB3 was underway.  But I do remember that we had a big banner in the hallway that said &amp;quot;OBJECT BASIC: Everything BASIC evolves!&amp;quot;

Indeed, Silver was the code name for VBA3 and Ruby was the code name for VB3.  VBScript didn't come along until many years later, and it never really had a code name.</description></item><item><title>RE: What are the VBScript reference semantics for object members?</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx#53011</link><pubDate>Wed, 17 Sep 2003 15:20:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:53011</guid><dc:creator>Ziv Caspi</dc:creator><description>Rezrov? Frob?

Nice to see someone still remembers ye good olde Infocom days...</description></item><item><title>RE: What are the VBScript reference semantics for object members?</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx#53012</link><pubDate>Thu, 18 Sep 2003 14:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:53012</guid><dc:creator>Stephen Sulzer</dc:creator><description>
My memory tells me, from being an intern on VB3 too, way back when, that:

&amp;quot;Object Basic&amp;quot; (OB) was the code name for VBA. It was a rewrite of the Basic language engine for VB4, to include built-in support for OLE Automation. VBA of course was also embedded into the Office products. I thought &amp;quot;Silver&amp;quot; was another original codename for the OB/VBA engine. OB was developed in parallel with VB3. VB 1 thru 3 used the old &amp;quot;EB&amp;quot; (Embedded Basic) language engine.  

&amp;quot;Thunder&amp;quot; was the code name for VB1 (and maybe VB2 and 3 too). &amp;quot;Ruby&amp;quot; was the codename of the VB forms engine component, which lived up thru VB6.
</description></item><item><title>In, Out, In-Out, Make Up Your Mind Already</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx#75980</link><pubDate>Thu, 19 Feb 2004 04:54:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:75980</guid><dc:creator>Fabulous Adventures In Coding</dc:creator><description>I was talking about reference types vs. by-reference variables a while back. Recall that both JScript and VBScript have reference types (ie, objects) but JScript does not have by-reference variables. COM supports passing variable references around, but unfortunately the intersection of early-bound COM and late-bound IDispatch is a little bit goofy.&lt;br&gt;</description></item><item><title>re: Aaargh, Part Six: One More Thing About Comments</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx#127264</link><pubDate>Thu, 06 May 2004 20:05:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:127264</guid><dc:creator>Fabulous Adventures In Coding</dc:creator><description /></item><item><title>More On ByRef vs ByVal</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx#127268</link><pubDate>Thu, 06 May 2004 20:08:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:127268</guid><dc:creator>Fabulous Adventures In Coding</dc:creator><description>It occurs to me that there may be some confusion about what exactly </description></item><item><title>Chronological Index</title><link>http://blogs.msdn.com/ericlippert/archive/2003/09/15/what-are-the-vbscript-reference-semantics-for-object-members.aspx#427920</link><pubDate>Fri, 10 Jun 2005 23:55:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:427920</guid><dc:creator>Fabulous Adventures In Coding</dc:creator><description>2003/09/12 What's Up With Hungarian Notation? 2003/09/12 Eric's Complete Guide To BSTR Semantics 2003/09/12...</description></item></channel></rss>