Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8223971
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T14:53:45+00:00 2026-06-07T14:53:45+00:00

For example, {include ‘path/to/template.tpl’} ? There’s no mention in the documentation of said format,

  • 0

For example, {include 'path/to/template.tpl'}?

There’s no mention in the documentation of said format, but it seems to work identically to:

{include file='path/to/template.tpl'}

Is this a quirk, or by design? I prefer the tidier syntax for when I’m not passing additional vars, but want to be sure it’s an accepted format (ver. 3.0.7).

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-07T14:53:47+00:00Added an answer on June 7, 2026 at 2:53 pm

    {include "foo"}, {extend "foo"} etc. are shorthand notations (deliberately) introduced in Smarty3. It is safe to use them. There are a bunch of these, e.g. {foreach $foo as $bar} (compared to {foreach from=$foo item="bar"}). They don’t differ performance-wise, so it really just boils down to your personal / team preference.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

The title is pretty self-explanatory, but here's a simplified example: #include <cstdio> template <typename
Is there anyway I can modify this code example #include <stdlib.h> #include <iostream> class
Why does tuple documentation say to use, for example: #include boost/tuple/tuple.hpp and not #include
Consider next example : #include <iostream> #include <typeinfo> template< int N, typename T >
Consider next example : #include <iostream> template< int a > void foo(); int main(int
Hi i have this command pattern example from the web , but there is
Please consider the following example: #include <string> #include <vector> using std::string; using std::vector; template
Example #include <vector> #include <cassert> template <typename Cont, typename... Rest> void f(Cont& c, Rest&...
Example: #include <iostream> using namespace std; int main() { wchar_t en[] = LHello; wchar_t
Consider this example: #include <iostream> class myclass { public: void print() { std::cout <<

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.