Differences

This shows you the differences between two versions of the page.

--- uphp:uphp_language_basics [2019/07/22 06:20]
admin
+++ uphp:uphp_language_basics [2019/07/22 06:52]
admin
@@ Line 1: / Line 1: @@
-======uPHP Blockly Development======
+======uPHP Language Basics======
-Blockly is a visual programming editor developed by Google.  We have integrated blockly with all the uPHP functions to make programming easier.  Blockly scripts can be automatically hooked to various parts of the system from the interface.
+The following sections describe how to work with uPHP scripts.
-Visual uPHP scripts need to be generated or run in order for the uPHP code to be created.  Visual uPHP scripts have the extension .cgx whereas generated scripts will have a .cgi extension.
+=====uPHP Tags=====
-{{:uphp:blockly_home.png?200|}}
+When Wattmon parses a file, it looks for opening and closing tags, which are ''<?'' and ''?>'' respectively. This tells Wattmon to start and stop interpreting the uPHP code between them. Parsing in this manner allows you to integrate script code within an HTML file as everything outside of a pair of opening and closing tags is ignored by the uPHP parser.
-=====Programmer Reference=====
+<code php>
+Some text
+<?
+  print(‘hello, uPHP’);
+?>
+Some more text
+</code>
-  * [[functions|uPHP Function Reference]] - The entire function list (advanced)
+In addition, you can integrate multiple code blocks within a page, even if it is within a uPHP code block.  For example if you wished to display a block of HTML based on a uPHP condition, it would go something like this:
-  * [[uPHP Special Variables]] - Special arrays that are populated automatically before a script is run
+<code php>
+<?
+  If ($mycondition > 5) {
+    ?> This will only be output if my condition > 5 <?
+  } else {
+    ?> This will be output if the first condition is not true. <?
+  }
+?>
+</code>
+=====Instruction Separation=====
+As in C and PHP, uPHP requires instructions to be terminated with a semicolon at the end of each statement. The closing tag of a block of uPHP code automatically implies a semicolon; you do not need to have a semicolon terminating the last line of a uPHP block. The closing tag for the block will include the immediately trailing newline if one is present.
+=====Comments=====
+uPHP supports 'C', 'C++' and Unix shell-style (Perl style) comments. For example:
+<code php>
+<?
+  // comment 1
+  $x=1;
+  # comment2
+  $x=2;
+  print($x);
+  /* comment 3 */
+  $x=3;
+  print($x);
+?>
+</code>
+The "one-line" comment styles only comment to the end of the line or the current block of uPHP code, whichever comes first. This means that HTML code after ''%%//%% ... ?>'' or ''# ... ?>'' WILL be printed: ''?>'' breaks out of uPHP mode and returns to HTML mode, and ''%%//%%'' or ''#'' cannot influence that.
+'C' style comments end at the first ''*/'' encountered. Make sure you don't nest 'C' style comments. It is easy to make this mistake if you are trying to comment out a large block of code.
+<code php>
+<?
+/*
+echo 'This is a test'; /* This comment will cause a problem */
+echo 'Print this also';
+*/
+?>
+</code>
+=====Programmer Reference=====
+  * [[.functions:uphp_function_reference|uPHP Reference]]
+  * [[uPHP Special Variables]]

Wattmon Documentation Wiki

User Tools

Site Tools

Differences

Page Tools