Re: [Help-source-highlight] Regular Expression Explanation for 'function

help-source-highlight

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-source-highlight] Regular Expression Explanation for 'function

From:	Peter Willis
Subject:	Re: [Help-source-highlight] Regular Expression Explanation for 'function.lang'
Date:	Fri, 27 May 2011 13:53:20 -0700
User-agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10

Hello,

There is a 'Wikipedia' page for IDL located at:
http://en.wikipedia.org/wiki/IDL_(programming_language)

There is a complete IDL programming manual located:

http://idlastro.gsfc.nasa.gov/idl_html_help/Programming_in_IDL.html

Normally procedures an functions are called on one line unless
the line exceeds 64 (?) characters. In that case the line may use
'$' symbol to continue the call statement on the next line.

Procedures do not return values, hence they are never called
as variables.

Functions can happen in-line anywhere.

Commas are also used as delimiters for array members in IDL.

Below is the language definition for rsiidl.lang .


'procedure.lang' is just a duplicate of 'function.lang'
at this point.

Best Regards,


Peter

//////////RSIIDL.LANG BEGIN///////////////////////////

preproc = "include|include_once|require|require_once"

comment start ";"

include "number.lang"

string delim "\"" "\"" escape "\\" multiline
string delim "'" "'"  escape "\\" multiline

D_DIMSET|HDF_DFSD_ENDSLICE|HDF_DFSD_GETDATA|HDF_DFSD_GETINFO|HDF_DFSD_GETSLICE|HDF_DFSD_PUTSLICE|HDF_DFSD_READREF|HDF_DFSD_SETINFO|HDF_DFSD_STARTSLICE|HDF_DUPDD|HDF_EXISTS|HDF_ISHDF|HDF_LIB_INFO|HDF_NEWREF|HDF_NUMBER|HDF_OPEN|HDF_GR_ATTRINFO|HDF_SD_ATTRFIND|HDF_SD_ATTRINFO|HDF_SD_ATTRSET|HDF_SD_CREATE|HDF_SD_DIMGET|HDF_SD_DIMGETID|HDF_SD_DIMSET|HDF_SD_END|HDF_SD_ENDACCESS|HDF_SD_FILEINFO|HDF_SD_GETDATA|HDF_SD_GETINFO|HDF_SD_IDTOREF|HDF_SD_ISCOORDVAR|HDF_SD_NAMETOINDEX|HDF_SD_REFTOINDEX|HDF_SD_SELECT|HDF_SD_SETEXTFILE|HDF_SD_SETINFO|HDF_SD_START|HDF_VD_ATTACH|HDF_VD_DETACH|HDF_VD_FDEFINE|HDF_VD_FEXIST|HDF_VD_FIND|HDF_VD_GET|HDF_VD_GETID|HDF_VD_GETINFO|HDF_VD_GETNEXT|HDF_VD_INSERT|HDF_VD_ISVD|HDF_VD_ISVG|HDF_VD_LONE|HDF_VD_READ|HDF_VD_SEEK|HDF_VD_SETINFO|HDF_VD_WRITE|HDF_VG_ADDTR|HDF_VG_ATTACH|HDF_VG_DETACH|HDF_VG_GETID|HDF_VG_GETINFO|HDF_VG_GETNEXT|HDF_VG_GETTR|HDF_VG_GETTRS|HDF_VG_INQTR|HDF_VG_INSERT|HDF_VG_ISVD|HDF_VG_ISVG|HDF_VG_LONE|HDF_VG_NUMBER|HDF_VG_SETINFO|NCDF_ATTCOP
Y|NCDF_ATTDEL|NCDF_ATTGET|NCDF_ATTINQ|NCDF_ATTNAME|NCDF_ATTPUT|NCDF_ATTRENAME|NCDF_CLOSE|NCDF_CONTROL|NCDF_CREATE|NCDF_DIMDEF|NCDF_DIMID|NCDF_DIMINQ|NCDF_DIMRENAME|NCDF_EXISTS|NCDF_INQUIRE|NCDF_OPEN|NCDF_VARDEF|NCDF_VARGET|NCDF_VARGET1|NCDF_VARID|NCDF_VARINQ|NCDF_VARPUT|NCDF_VARRENAME|ENDELSE|RETURN"

comment delim "/*" "*/" multiline nested

type = '(?:\$[#]?|@|%)[[:word:]]+'

include "symbols.lang"

cbracket = "{|}"

include "function.lang"
include "procedure.lang"

variable = '[[:upper:]][[:word:]]*|_'

///////////////////RSIIDL.LANG END////////////////////////////////




On 5/27/2011 1:57 AM, Lorenzo Bettini wrote:

Hi

do procedure (and functions) are always called on a line?
I mean, is the procedure name always at the beginning of a line
(possibly with some spaces before)?

Are commas used also in other contexts besides function and procedure
invocation?

cheers
Lorenzo

P.S. some examples of programs might be useful to do some tests; have
you already a partial language definition for IDL to start from?

On 05/24/2011 05:27 PM, Peter Willis wrote:

On 5/23/2011 7:10 AM, Lorenzo Bettini wrote:

(?=\()

checks whether after the name there's a ( but does not consume it

can the syntax of your procedure definition be identified with a regular
expression?

Can you make some examples of procedures?

cheers
Lorenzo



Hello,

In 'IDL' procedures are *called* in the following way:

PROCEDURE_NAME , ARGUMENT_1, ARGUMENT_2, ARGUMENT_3, .... , ARGUMENT_N

As you can see no brackets or parenthesis are used. The problem here is
a regex would need to deal with only the first case of the
comma positioned after 'PROCEDURE_NAME' and ignore all other groupings
until the end of the statement.

There is also on other problem in that statements can use continuation
where a '$' indicates the current statement continues on to the
next line:

PROCEDURE_NAME , ARGUMENT_1, $
ARGUMENT_2, ARGUMENT_3, $
.... , ARGUMENT_N

In this case regex needs to distinguish between the case of
'PRODEDURE_NAME' and cases where the statement has been continued.
ie: not highlight 'ARGUMENT_2' due to the comma following there.


Declarations for *both* functions and procedures are written in
similar ways. The difference is only the 'RETURN' value in the case
of functions:

FUNCTION function_name, arg_1, arg_2 $
arg_3, arg_4, ...., arg_n
....<PROGRAM STATEMENTS>...

RETURN, some_value
END


PRO procedure_name, arg_1, arg_2 arg_3, arg_4, ....,$
arg_n
....<PROGRAM STATEMENTS>...
END



Best Regards,


Peter

_______________________________________________
Help-source-highlight mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/help-source-highlight

[Prev in Thread]

Current Thread

[Next in Thread]

[Help-source-highlight] Regular Expression Explanation for 'function.lang', Peter Willis, 2011/05/20
- Re: [Help-source-highlight] Regular Expression Explanation for 'function.lang', Lorenzo Bettini, 2011/05/23
  - Re: [Help-source-highlight] Regular Expression Explanation for 'function.lang', Peter Willis, 2011/05/24
    - Re: [Help-source-highlight] Regular Expression Explanation for 'function.lang', Lorenzo Bettini, 2011/05/27
    - Re: [Help-source-highlight] Regular Expression Explanation for 'function.lang', Peter Willis <=

Prev by Date: Re: [Help-source-highlight] Regular Expression Explanation for 'function.lang'
Previous by thread: Re: [Help-source-highlight] Regular Expression Explanation for 'function.lang'
Index(es):
- Date
- Thread