<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	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:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Include, Include_once, Require, Require_once</title>
	<atom:link href="http://www.lgr.ca/blog/2008/06/include-include_once-require-require_once.html/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lgr.ca/blog/2008/06/include-include_once-require-require_once.html</link>
	<description>Bringing the Internet into Focus!</description>
	<lastBuildDate>Thu, 15 Dec 2011 22:47:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: John</title>
		<link>http://www.lgr.ca/blog/2008/06/include-include_once-require-require_once.html#comment-1273</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 16 Oct 2009 10:08:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.lgr.ca/blog/?p=409#comment-1273</guid>
		<description>The only possible argument for the defence of not using templating is to enable joint collaboration on a website.  Once you start including the &#039;includes&#039; visual design in the likes of Dreamweaver becomes much more difficult.

Anyway, I came to this article for the include, require information so thanks a lot.</description>
		<content:encoded><![CDATA[<p>The only possible argument for the defence of not using templating is to enable joint collaboration on a website.  Once you start including the &#8216;includes&#8217; visual design in the likes of Dreamweaver becomes much more difficult.</p>
<p>Anyway, I came to this article for the include, require information so thanks a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LGR</title>
		<link>http://www.lgr.ca/blog/2008/06/include-include_once-require-require_once.html#comment-734</link>
		<dc:creator>LGR</dc:creator>
		<pubDate>Tue, 03 Jun 2008 00:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.lgr.ca/blog/?p=409#comment-734</guid>
		<description>Well essentially that is what I do. I put the site into a templating system when I create a new website. I just find it hard to believe that these organizations that I am working for had so called &quot;professionals&quot; use only static HTML and no templating system at all. These were not sites that were built five or six years ago. They are sites that were built only a year or two ago. All static HTML. I won&#039;t even get started about how the HTML is to begin with.</description>
		<content:encoded><![CDATA[<p>Well essentially that is what I do. I put the site into a templating system when I create a new website. I just find it hard to believe that these organizations that I am working for had so called &#8220;professionals&#8221; use only static HTML and no templating system at all. These were not sites that were built five or six years ago. They are sites that were built only a year or two ago. All static HTML. I won&#8217;t even get started about how the HTML is to begin with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://www.lgr.ca/blog/2008/06/include-include_once-require-require_once.html#comment-733</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Mon, 02 Jun 2008 18:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.lgr.ca/blog/?p=409#comment-733</guid>
		<description>I think I&#039;d go even further and say that if you are using things like common headers and menus you should be using a templating system.  There are plenty out there, and even if you don&#039;t like them, it&#039;s pretty easy to write your own.  The added bonus is that you can get a HTML designer in to update the site without having to touch any php (providing you keep the content semantic and well structured).

But good point about the differences between include and require.</description>
		<content:encoded><![CDATA[<p>I think I&#8217;d go even further and say that if you are using things like common headers and menus you should be using a templating system.  There are plenty out there, and even if you don&#8217;t like them, it&#8217;s pretty easy to write your own.  The added bonus is that you can get a HTML designer in to update the site without having to touch any php (providing you keep the content semantic and well structured).</p>
<p>But good point about the differences between include and require.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 5/17 queries in 0.027 seconds using disk: basic
Object Caching 385/386 objects using disk: basic
Content Delivery Network via cdn.lgr.ca

Served from: www.lgr.ca @ 2012-02-11 16:02:33 -->
