Databases
StackOverflow2013
Postsdbo
PORun a Conditional Using PHP Version
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORun a Conditional Using PHP Version
    primarykey
    data
    text
    <p>So my goal right now is to detect the user's PHP version (not an issue), and then run an if else based on it</p> <p>So if I write something like this:</p> <pre><code>if (PHP =&gt; 5.3){ // call a function anonymously } else { // if user does not have 5.3, this else block disables the feature. } </code></pre> <p>the issue I'm having is I want to use PHP's anonymous functions if the user has 5.3 or greater (since they were introduced in PHP 5.3) and an alternative if they have an older version. The problem is, of course, that if a user has PHP 5.2.17 for instance, that while that if statement will never evaluate as true, a fatal error will be thrown for syntax since the anonymous function call looks like a syntax error to PHP 5.2.17</p> <p>Is there a way to do something like the above? The only work around I've found is to put the stuff in the if in a new file, and the stuff in the else in another, and do something like this:</p> <pre><code>$version = '5.2';//user's current version cut to the nearest x.y, ex 5.3, 5.4, 5.5 // Remove the period here, so we have 5.2 require 'function'.$version.'.php'; </code></pre> <p>Now this will work fine, since function53.php will never be loaded for a 5.2 user. However it's not ideal to have to use separate files.</p> <p>After reading the comment's to Ales's quesiton, something like this:</p> <pre><code>if ($version &gt; '5.3'){ // require one file } else{ // require another } </code></pre> <p>Will not work. PHP's compiler will run both files on compilation checking for syntax errors before execution and throw the error I'm trying to avoid. The only way for the file method to work is to dynamically pick a file based on version number. This requires a seperate file for every x.y release from PHP 4 and 5. Not ideal.</p> <p>On Alex's answer, it works fine. We're talking one line of eval (required to hide the anonymous function call), versus the proposed tons of files.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChris
    1. USChris
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTDuplicate
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORun a Conditional Using PHP Version
      1. This table or related slice is empty.
      1. VTClose
    2. VO
      singulars
      1. PORun a Conditional Using PHP Version
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORun a Conditional Using PHP Version
      1. This table or related slice is empty.
      1. VTClose
    1. CO[version_compare()](http://php.net/manual/en/function.version-compare.php) ?
      singulars
      1. PORun a Conditional Using PHP Version
      1. USnice ass
    2. COWay, *way* too much work. You're seriously going to write *two copies* of all your code, just to take advantage of new syntax, when the old syntax *works fine* in both versions?
      singulars
      1. PORun a Conditional Using PHP Version
      1. USmeagar
    3. CODo you really want to duplicate code for this? You should have *one* implementation of that function in the syntax that the lowest PHP version you want to support can handle. It'll work the same, you shouldn't rewrite it as closure *as well* just because you can.
      singulars
      1. PORun a Conditional Using PHP Version
      1. USdeceze
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload