<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: How do you think about virtual buses?</title>
	<link>http://blogs.mathworks.com/seth/2008/04/11/how-do-you-think-about-virtual-buses/</link>
	<description>This blog is about Simulink.</description>
	<pubDate>Mon, 23 Nov 2009 01:15:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Vijay Swaminathan</title>
		<link>http://blogs.mathworks.com/seth/2008/04/11/how-do-you-think-about-virtual-buses/#comment-153</link>
		<dc:creator>Vijay Swaminathan</dc:creator>
		<pubDate>Wed, 16 Apr 2008 15:20:32 +0000</pubDate>
		<guid>http://blogs.mathworks.com/seth/2008/04/11/how-do-you-think-about-virtual-buses/#comment-153</guid>
		<description>I still think of both virtual and non-virtual buses as struct's. The distinction in my mind being (and this is a very loose analogy):

Non-virtual Buses: The struct fields are Pass by value.

Virtual Buses : The struct fields are Pass by reference.</description>
		<content:encoded><![CDATA[<p>I still think of both virtual and non-virtual buses as struct&#8217;s. The distinction in my mind being (and this is a very loose analogy):</p>
<p>Non-virtual Buses: The struct fields are Pass by value.</p>
<p>Virtual Buses : The struct fields are Pass by reference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth</title>
		<link>http://blogs.mathworks.com/seth/2008/04/11/how-do-you-think-about-virtual-buses/#comment-152</link>
		<dc:creator>Seth</dc:creator>
		<pubDate>Wed, 16 Apr 2008 12:20:35 +0000</pubDate>
		<guid>http://blogs.mathworks.com/seth/2008/04/11/how-do-you-think-about-virtual-buses/#comment-152</guid>
		<description>@Paul - I think it is natural to equate the bus to a struct.  The distinction between virtual and nonvirtual buses is subtle and often doesn't matter when modeling.  There are additional constraints on nonvirtual buses, like sample time agreement which we will mention in the next post.  Thanks for commenting!</description>
		<content:encoded><![CDATA[<p>@Paul - I think it is natural to equate the bus to a struct.  The distinction between virtual and nonvirtual buses is subtle and often doesn&#8217;t matter when modeling.  There are additional constraints on nonvirtual buses, like sample time agreement which we will mention in the next post.  Thanks for commenting!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul J.</title>
		<link>http://blogs.mathworks.com/seth/2008/04/11/how-do-you-think-about-virtual-buses/#comment-150</link>
		<dc:creator>Paul J.</dc:creator>
		<pubDate>Sun, 13 Apr 2008 23:34:04 +0000</pubDate>
		<guid>http://blogs.mathworks.com/seth/2008/04/11/how-do-you-think-about-virtual-buses/#comment-150</guid>
		<description>Seth,

My mental model of a bus was that of a struct with the signals in the bus corresponding to the struct fieldnames.  After reading your article, I went back to the documentation and now I think that my view is more aligned with a non-virtual bus, which I've not yet had to use.  So I'm looking forward to your article on the non-virtual bus, when to use it, when it's required, how to get the signals from it into the workspace, etc.

Thanks,
Paul</description>
		<content:encoded><![CDATA[<p>Seth,</p>
<p>My mental model of a bus was that of a struct with the signals in the bus corresponding to the struct fieldnames.  After reading your article, I went back to the documentation and now I think that my view is more aligned with a non-virtual bus, which I&#8217;ve not yet had to use.  So I&#8217;m looking forward to your article on the non-virtual bus, when to use it, when it&#8217;s required, how to get the signals from it into the workspace, etc.</p>
<p>Thanks,<br />
Paul</p>
]]></content:encoded>
	</item>
</channel>
</rss>
