<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
<channel>
	<title>Comments for Verilab Blog</title>
	
	<link>http://www.verilab.com/blog</link>
	<description>Verilab</description>
	<pubDate>Fri, 22 Jan 2010 20:54:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/CommentsForVerilabBlog" /><feedburner:info uri="commentsforverilabblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:browserFriendly></feedburner:browserFriendly><item>
		<title>Comment on Reuseless Code by Pandithurai Sangaiyah</title>
		<link>http://www.verilab.com/blog/2007/09/reuseless-code/#comment-165</link>
		<dc:creator>Pandithurai Sangaiyah</dc:creator>
		<pubDate>Tue, 20 Jan 2009 17:21:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/2007/09/reuseless-code/#comment-165</guid>
		<description>Really Good explanation which clear my basic doubt.</description>
		<content:encoded><![CDATA[<p>Really Good explanation which clear my basic doubt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Litterick’s OCP-IP newsletter article uses Verilab’s OCP uVC VIP as an example by One Nanometer</title>
		<link>http://www.verilab.com/blog/2009/01/littericks-ocp-ip-newletter-article-uses-verilabs-ocp-uvc-vip-as-an-example/#comment-164</link>
		<dc:creator>One Nanometer</dc:creator>
		<pubDate>Fri, 09 Jan 2009 08:31:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/?p=79#comment-164</guid>
		<description>Great Blog you have there! Wondering if you could link us back?</description>
		<content:encoded><![CDATA[<p>Great Blog you have there! Wondering if you could link us back?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DAC 2008 Presentations Now Posted by JL Gray</title>
		<link>http://www.verilab.com/blog/2008/07/dac-2008-presentations-now-posted/#comment-163</link>
		<dc:creator>JL Gray</dc:creator>
		<pubDate>Thu, 25 Sep 2008 23:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/2008/07/dac-2008-presentations-now-posted/#comment-163</guid>
		<description>Sean,

I believe this should be fixed (again).  We've made some other modifications which I hope will resolve the problem once and for all.  If you're still seeing issues please let me know. 

Thanks,  

JL</description>
		<content:encoded><![CDATA[<p>Sean,</p>
<p>I believe this should be fixed (again).  We&#8217;ve made some other modifications which I hope will resolve the problem once and for all.  If you&#8217;re still seeing issues please let me know. </p>
<p>Thanks,  </p>
<p>JL</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DAC 2008 Presentations Now Posted by Sean</title>
		<link>http://www.verilab.com/blog/2008/07/dac-2008-presentations-now-posted/#comment-162</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Mon, 22 Sep 2008 02:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/2008/07/dac-2008-presentations-now-posted/#comment-162</guid>
		<description>The posts feed is still compromised. (Or has been compromised again.)

Drop me an email if you want so see the feed contents that I see.

http://www.verilab.com/blog/feed/ on NewsGator.

-Sean</description>
		<content:encoded><![CDATA[<p>The posts feed is still compromised. (Or has been compromised again.)</p>
<p>Drop me an email if you want so see the feed contents that I see.</p>
<p><a href="http://www.verilab.com/blog/feed/" rel="nofollow">http://www.verilab.com/blog/feed/</a> on NewsGator.</p>
<p>-Sean</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DAC 2008 Presentations Now Posted by JL Gray</title>
		<link>http://www.verilab.com/blog/2008/07/dac-2008-presentations-now-posted/#comment-160</link>
		<dc:creator>JL Gray</dc:creator>
		<pubDate>Wed, 20 Aug 2008 15:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/2008/07/dac-2008-presentations-now-posted/#comment-160</guid>
		<description>James,

Thanks for the heads up on this.  Turns out our blog software was somewhat out of date and a few of the posts/comments had been compromised.  The issue should be resolved now. Let me know if you're still seeing any issues.

Take care,

JL</description>
		<content:encoded><![CDATA[<p>James,</p>
<p>Thanks for the heads up on this.  Turns out our blog software was somewhat out of date and a few of the posts/comments had been compromised.  The issue should be resolved now. Let me know if you&#8217;re still seeing any issues.</p>
<p>Take care,</p>
<p>JL</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DAC 2008 Presentations Now Posted by James Colgan</title>
		<link>http://www.verilab.com/blog/2008/07/dac-2008-presentations-now-posted/#comment-159</link>
		<dc:creator>James Colgan</dc:creator>
		<pubDate>Sun, 17 Aug 2008 16:51:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/2008/07/dac-2008-presentations-now-posted/#comment-159</guid>
		<description>Hi,

We've implemented a feed reader on the Xuropa Platform and have found that the verilab RSS feed has been compromised.  

From the code, it looks like it's within the comments feed (a usual point of attack for spammers), even though there is a captcha system in place on your site.  The junk may have been injected over at feedburner instead, but I can't tell from the code.

We still have your feed on the platform, but the comments are a mess and won't be included.  Also, it does make your feed very "heavy".

I've emailed you the feed file separately.

James</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>We&#8217;ve implemented a feed reader on the Xuropa Platform and have found that the verilab RSS feed has been compromised.  </p>
<p>From the code, it looks like it&#8217;s within the comments feed (a usual point of attack for spammers), even though there is a captcha system in place on your site.  The junk may have been injected over at feedburner instead, but I can&#8217;t tell from the code.</p>
<p>We still have your feed on the platform, but the comments are a mess and won&#8217;t be included.  Also, it does make your feed very &#8220;heavy&#8221;.</p>
<p>I&#8217;ve emailed you the feed file separately.</p>
<p>James</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SystemVerilog Gotcha: (when copying) a struct is not a class by another name by Jason Sprott</title>
		<link>http://www.verilab.com/blog/2008/01/gotcha-when-copying-a-struct-is-not-a-class-by-a-different-name/#comment-155</link>
		<dc:creator>Jason Sprott</dc:creator>
		<pubDate>Wed, 23 Jan 2008 08:28:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/2008/01/gotcha-when-copying-a-struct-is-not-a-class-by-a-different-name/#comment-155</guid>
		<description>Hi Daniel

Thanks for pointing out that error (now corrected). I fixed the variable names and also added the new() of the elements in Y[], inside the foreach loop, for clarity.

Yes, when a struct is copied the values are copied. When a class is copied the reference is copied, or a shallow copy is taken (as described in IEEE1800-2005, Section 7.11). I find people typically remember that when they are dealing with the class itself. When classes are inside something else, it's easy to forget, because we are copying the thing and may not even have visibility of its contents. Arrays of classes fall into that category, but a class composed of other classes is another big one to watch.

There is no method for a deep copy/clone defined in the SystemVerilog language. Both the AVM and VMM define methods for copying objects as part of the methodology. In Vera we had a built-in method called object_copy() as part of the language. This provided a deep copy of any object, without you having to write anything yourself. I found it useful, but the problem was that there was no control, so you could end up copying something *very* large.

Of course when writing custom copy functions we sometimes put bugs in them too.

Jason</description>
		<content:encoded><![CDATA[<p>Hi Daniel</p>
<p>Thanks for pointing out that error (now corrected). I fixed the variable names and also added the new() of the elements in Y[], inside the foreach loop, for clarity.</p>
<p>Yes, when a struct is copied the values are copied. When a class is copied the reference is copied, or a shallow copy is taken (as described in IEEE1800-2005, Section 7.11). I find people typically remember that when they are dealing with the class itself. When classes are inside something else, it&#8217;s easy to forget, because we are copying the thing and may not even have visibility of its contents. Arrays of classes fall into that category, but a class composed of other classes is another big one to watch.</p>
<p>There is no method for a deep copy/clone defined in the SystemVerilog language. Both the AVM and VMM define methods for copying objects as part of the methodology. In Vera we had a built-in method called object_copy() as part of the language. This provided a deep copy of any object, without you having to write anything yourself. I found it useful, but the problem was that there was no control, so you could end up copying something *very* large.</p>
<p>Of course when writing custom copy functions we sometimes put bugs in them too.</p>
<p>Jason</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SystemVerilog Gotcha: (when copying) a struct is not a class by another name by Daniel Pörsch</title>
		<link>http://www.verilab.com/blog/2008/01/gotcha-when-copying-a-struct-is-not-a-class-by-a-different-name/#comment-154</link>
		<dc:creator>Daniel Pörsch</dc:creator>
		<pubDate>Tue, 22 Jan 2008 13:37:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/2008/01/gotcha-when-copying-a-struct-is-not-a-class-by-a-different-name/#comment-154</guid>
		<description>Hi Verilab,

just a short note, you define A,B as classes and X,Y as structs in the code, but refer to A,B as structs and X,Y as classes in the text. This is confusing, I guess the text is correct?!

What would happen if I didn't have arrays of classes/structs but a single class and a single struct, I guess the same rule would apply, i.e. copy-by-reference for classes and copy-by-value for structs?

There's no Copy-Constructor in SV, is there? Would be handy ...

Rgds,
Daniel</description>
		<content:encoded><![CDATA[<p>Hi Verilab,</p>
<p>just a short note, you define A,B as classes and X,Y as structs in the code, but refer to A,B as structs and X,Y as classes in the text. This is confusing, I guess the text is correct?!</p>
<p>What would happen if I didn&#8217;t have arrays of classes/structs but a single class and a single struct, I guess the same rule would apply, i.e. copy-by-reference for classes and copy-by-value for structs?</p>
<p>There&#8217;s no Copy-Constructor in SV, is there? Would be handy &#8230;</p>
<p>Rgds,<br />
Daniel</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on You’ve Got [Mail|Bugs]? by Dusty</title>
		<link>http://www.verilab.com/blog/2007/12/youve-got-mailbugs/#comment-153</link>
		<dc:creator>Dusty</dc:creator>
		<pubDate>Sun, 16 Dec 2007 07:26:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/2007/12/youve-got-mailbugs/#comment-153</guid>
		<description>E-mail can be used for to-do's with folders.  Your inbox should be just that, an inbox.  If it's informative, it can go into another folder.  If it requires action, it goes in Todo.  If it's fluff, scan it over and throw it in the trash.  That's probably why using a to-do list or bug tracker for e-mail correspondence doesn't work as well.  There's quite a bit of fluff that you get through e-mail.

On the other side of things, tracking bugs through e-mail would limit all kinds of metrics and change tracking that management, bean counters, and excel graph afficiandos everywhere love.  This is a big part of some process driven businesses.  However, there's nothing to say you can't use a bug tracker centralized database with e-mail.  Send your bug report to bugs@myproj and it could be tracked by the daemon reading it while sending an e-mail to the  developer to look at it.  It's all about how you format the text and if the daemon is smart enough to figure it all out so you aren't wasting more time trying to format your e-mail message.</description>
		<content:encoded><![CDATA[<p>E-mail can be used for to-do&#8217;s with folders.  Your inbox should be just that, an inbox.  If it&#8217;s informative, it can go into another folder.  If it requires action, it goes in Todo.  If it&#8217;s fluff, scan it over and throw it in the trash.  That&#8217;s probably why using a to-do list or bug tracker for e-mail correspondence doesn&#8217;t work as well.  There&#8217;s quite a bit of fluff that you get through e-mail.</p>
<p>On the other side of things, tracking bugs through e-mail would limit all kinds of metrics and change tracking that management, bean counters, and excel graph afficiandos everywhere love.  This is a big part of some process driven businesses.  However, there&#8217;s nothing to say you can&#8217;t use a bug tracker centralized database with e-mail.  Send your bug report to bugs@myproj and it could be tracked by the daemon reading it while sending an e-mail to the  developer to look at it.  It&#8217;s all about how you format the text and if the daemon is smart enough to figure it all out so you aren&#8217;t wasting more time trying to format your e-mail message.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reuseless Code by Sandeep Gor</title>
		<link>http://www.verilab.com/blog/2007/09/reuseless-code/#comment-152</link>
		<dc:creator>Sandeep Gor</dc:creator>
		<pubDate>Wed, 12 Dec 2007 08:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/2007/09/reuseless-code/#comment-152</guid>
		<description>Nice explaination to my dilemma while developing verification environment. Lately, I started realizing what you explained as "reuseless code". In my last project, my verification environment implementation made me think "whether that perticular reusable code was really reusable? or was it required to implement it as resuable?"

Thanks for this post.

Best Regards,
Sandeep Gor.</description>
		<content:encoded><![CDATA[<p>Nice explaination to my dilemma while developing verification environment. Lately, I started realizing what you explained as &#8220;reuseless code&#8221;. In my last project, my verification environment implementation made me think &#8220;whether that perticular reusable code was really reusable? or was it required to implement it as resuable?&#8221;</p>
<p>Thanks for this post.</p>
<p>Best Regards,<br />
Sandeep Gor.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
