<?phpxml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
>
<channel>
<title>bibsonomyz.xyz / orensuggs00 / New</title>
<link>http://bibsonomyz.xyz</link>
<description>Your Source for Social News and Networking</description>
<pubDate>Wed, 21 Oct 2026 12:20:19 +0000</pubDate>
<language>en</language>
<item>
	<title><![CDATA[Has It Happened Yet?]]></title>
	<link>http://bibsonomyz.xyz/story.php?title=has-it-happened-yet</link>
	<source url="http://bibsonomyz.xyz/story.php?title=has-it-happened-yet"><![CDATA[Has It Happened Yet?]]></source>
	<description><![CDATA[If a job will get actually complex, this methodology of routing execution to the suitable part of the duty each time it is known as could get a bit furry if you really wanted to keep away from all pointless delays. I often use a CASE statement (referred to as "Select CASE" in Basic and "change" in C, but I named lots of my structure macros after Forth buildings) to steer the execution to the right a part of the routine depending on the state. ]]></description>
	<pubDate>Wed, 21 Oct 2026 12:20:19 +0000</pubDate>
	<author>orensuggs00</author>
	<category>News</category>
	<votes>1</votes>
	<guid>http://bibsonomyz.xyz/story.php?title=has-it-happened-yet</guid>
</item>

</channel>
</rss>
