Links in the source in the :active state

The key of the regex array defining what bracket group in a matched search to put after the replacement

Strict mode always applies

The key of the regex array defining what bracket group in a matched search to put before the replacement

Leave keywords found as the case that they are

Lowercase keywords found

Uppercase keywords found

The key of the regex array defining a custom keyword to use for this regexp's html tag class

Used in language files to mark comments

The ender for important parts of the source

GeSHi could not open a file for reading (generally a language file)

The header type passed to GeSHi->set_header_type() was invalid

The line number type passed to GeSHi->enable_line_numbers() was invalid

No sourcecode to highlight was specified

The language specified does not exist

Use fancy line numbers when building the result

Use a "div" to surround the source

Use nothing to surround the source

Use a "pre" to surround the source

Use a "table" to surround the source:

$linenumbers

$code>

this is essentially only a workaround for Firefox, see sf#1651996 or take a look at https://bugzilla.mozilla.org/show_bug.cgi?id=365805

Use a pre to wrap lines when line numbers are enabled or to wrap the whole code.

Links in the source in the :hover state

The language file directory for GeSHi @access private

Links in the source in the :link state

it's also important not to generate too long regular expressions be generous here... but keep in mind, that when reaching this limit we still have to close open patterns. 12k should do just fine on a 16k limit. @see GeSHi->optimize_regexp_list()

some old PHP / PCRE subpatterns only support up to xxx subpatterns in regular expressions. Set this to false if your PCRE lib is up to date @see GeSHi->optimize_regexp_list()

Strict mode *might* apply, and can be enabled or disabled by GeSHi->enable_strict_mode()

The key of the regex array defining any modifiers to the regular expression

Use normal line numbers when building the result

Use no line numbers when building the result

Number format to highlight binary numbers with a prefix 0b (C)

Number format to highlight binary numbers with a prefix %

Number format to highlight binary numbers with a suffix "b"

Number format to highlight floating-point numbers without support for scientific notation

Number format to highlight floating-point numbers without support for scientific notation

Number format to highlight floating-point numbers with support for scientific notation (E) and optional leading zero

Number format to highlight floating-point numbers with support for scientific notation (E) and required leading digit

Number format to highlight hex numbers with a prefix 0x

Number format to highlight hex numbers with a suffix of h

Basic number format for integers

Enhanced number format for integers like seen in C

Number format to highlight octal numbers with a leading zero

Number format to highlight octal numbers with a suffix of o

Used to work around missing PHP features

The key of the regex array defining what bracket group in a matched search to use as a replacement

The root directory for GeSHi

The key of the regex array defining what to search for

Tells GeSHi to be paranoid about security settings

The starter for important parts of the source

The version of this GeSHi file

Links in the source in the :visited state

abap.php -------- Author: Andres Picazo (andres@andrespicazo.com) Contributors: - Sandra Rossi (sandra.rossi@gmail.com) - Jacob Laursen (jlu@kmd.dk) Copyright: (c) 2007 Andres Picazo Release Version: 1.0.8.3 Date Started: 2004/06/04

ABAP language file for GeSHi.

Reference abap language documentation (abap 7.1) : http://help.sap.com/abapdocu/en/ABENABAP_INDEX.htm

ABAP syntax is highly complex, several problems could not be addressed, see TODO below if you dare ;-) Be aware that in ABAP language, keywords may be composed of several tokens, separated by one or more spaces or carriage returns (for example CONCATENATE 'hello' 'world' INTO string SEPARATED BY ' ') it's why we must decode them with REGEXPS. As there are many keywords with several tokens, I had to create a separate section in the code to simplify the reading. Be aware that some words may be highlighted several times like for "ref to data", which is first highlighted for "ref to data", then secondly for "ref to". It is very important to position "ref to" after "ref to data" otherwise "data" wouldn't be highlighted because of the previous highlight. Styles used : keywords are all displayed in upper case, and they are organized into 4 categories : 1) control statements (blue), 2) declarative statements (red-maroon), 3) other statements (blue-green), 4) keywords (violet). + GeSHi : literals (red) + symbols (green) + methods/attributes (mauve) + unchanged style for other words. Control, declarative and other statements are assigned URLs to sap documentation website: http://help.sap.com/abapdocu/en/ABAP.htm

CHANGES ------- 2009/02/25 (1.0.8.3) - Some more rework of the language file 2009/01/04 (1.0.8.2) - Major Release, more than 1000 statements and keywords added = whole abap 7.1 (Sandra Rossi) 2007/06/27 (1.0.0) - First Release

TODO ---- - in DATA data TYPE type, 2nd "data" and 2nd "type" are highlighted with data style, but should be ignored. Same problem for all words!!! This is quite impossible to solve it as we should define syntaxes of all statements (huge effort!) and use a lex or something like that instead of regexp I guess. - Some words are considered as being statement names (report, tables, etc.) though they are used as keyword in some statements. For example: FORM xxxx TABLES itab. It was arbitrary decided to define them as statement instead of keyword, because it may be useful to have the URL to SAP help for some of them. - if a comment is between 2 words of a keyword (for example SEPARATED "comment \n BY), it is not considered as a keyword, but it should! - for statements like "READ DATASET", GeSHi does not allow to set URLs because these statements are determined by REGEXPS. For "READ DATASET", the URL should be ABAPREAD_DATASET.htm. If a technical solution is found, be careful : URLs are sometimes not valid because the URL does not exist. For example, for "AT NEW" statement, the URL should be ABAPAT_ITAB.htm (not ABAPAT_NEW.htm). There are many other exceptions. Note: for adding this functionality within your php program, you can execute this code: function add_urls_to_multi_tokens( $matches ) { $url = preg_replace( "/[ \n]+/" , "_" , $matches[3] ); if( $url == $matches[3] ) return $matches[0] ; else return $matches[1]."".$matches[3]."".$matches[4]; } $html = $geshi->parse_code(); $html = preg_replace_callback( "£(zzz:(control|statement|data);\">)(.+?)()£s", "add_urls_to_multi_tokens", $html ); echo $html; - Numbers followed by a dot terminating the statement are not properly recognized

This file is part of GeSHi.

GeSHi is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

GeSHi is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with GeSHi; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA