1

/*

     2

 *  matiec - a compiler for the programming languages defined in IEC 61131-3

     3

 *

     4

 *  Copyright (C) 2003-2011  Mario de Sousa (msousa@fe.up.pt)

     5

 *

     6

 *  This program is free software: you can redistribute it and/or modify

     7

 *  it under the terms of the GNU General Public License as published by

     8

 *  the Free Software Foundation, either version 3 of thest_whitespaceLicense, or

     9

 *  (at your option) any later version.

    10

 *

    11

 *  This program is distributed in the hope that it will be useful,

    12

 *  but WITHOUT ANY WARRANTY; without even the implied warranty of

    13

 *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the

    14

 *  GNU General Public License for more details.

    15

 *

    16

 *  You should have received a copy of the GNU General Public License

    17

 *  along with this program.  If not, see <http://www.gnu.org/licenses/>.

    18

 *

    19

 *

    20

 * This code is made available on the understanding that it will not be

    21

 * used in safety-critical situations without a full and competent review.

    22

 */

    23

    24

/*

    25

 * An IEC 61131-3 compiler.

    26

 *

    27

 * Based on the

    28

 * FINAL DRAFT - IEC 61131-3, 2nd Ed. (2001-12-10)

    29

 *

    30

 */

    31

    32

/*

    33

 * Stage 1

    34

 * =======

    35

 *

    36

 * This file contains the lexical tokens definitions, from which

    37

 * the flex utility will generate a lexical parser function.

    38

 */

    39

    40

    41

    42

    43

/*****************************/

    44

/* Lexical Parser Options... */

    45

/*****************************/

    46

    47

/* The lexical analyser will never work in interactive mode,

    48

 * i.e., it will only process programs saved to files, and never

    49

 * programs being written inter-actively by the user.

    50

 * This option saves the resulting parser from calling the

    51

 * isatty() function, that seems to be generating some compile

    52

 * errors under some (older?) versions of flex.

    53

 */

    54

%option never-interactive

    55

    56

/* Have the lexical analyser use a 'char *yytext' instead of an

    57

 * array of char 'char yytext[??]' to store the lexical token.

    58

 */

    59

%pointer

    60

    61

    62

/* Have the lexical analyser ignore the case of letters.

    63

 * This will occur for all the tokens and keywords, but

    64

 * the resulting text handed up to the syntax parser

    65

 * will not be changed, and keep the original case

    66

 * of the letters in the input file.

    67

 */

    68

%option case-insensitive

    69

    70

/* Have the generated lexical analyser keep track of the

    71

 * line number it is currently analysing.

    72

 * This is used to pass up to the syntax parser

    73

 * the number of the line on which the current

    74

 * token was found. It will enable the syntax parser

    75

 * to generate more informatve error messages...

    76

 */

    77

%option yylineno

    78

    79

/* required for the use of the yy_pop_state() and

    80

 * yy_push_state() functions

    81

 */

    82

%option stack

    83

    84

/* The '%option stack' also requests the inclusion of 

    85

 * the yy_top_state(), however this function is not

    86

 * currently being used. This means that the compiler

    87

 * is complaining about the existance of this function.

    88

 * The following option removes the yy_top_state()

    89

 * function from the resulting c code, so the compiler 

    90

 * no longer complains.

    91

 */

    92

%option noyy_top_state

    93

    94

/* We will be using unput() in our flex code, so we cannot set the following option!... */

    95

/*

    96

%option nounput

    97

*/

    98

    99

/**************************************************/

   100

/* External Variable and Function declarations... */

   101

/**************************************************/

   102

   103

   104

%{

   105

/* Define TEST_MAIN to include a main() function.

   106

 * Useful for testing the parser generated by flex.

   107

 */

   108

/*

   109

#define TEST_MAIN

   110

*/

   111

/* If lexical parser is compiled by itself, we need to define the following

   112

 * constant to some string. Under normal circumstances LIBDIRECTORY is set

   113

 * in the syntax parser header file...

   114

 */

   115

#ifdef TEST_MAIN

   116

#define DEFAULT_LIBDIR "just_testing"

   117

#endif

   118

   119

   120

   121

/* Required for strdup() */

   122

#include <string.h>

   123

   124

/* Required only for the declaration of abstract syntax classes

   125

 * (class symbol_c; class token_c; class list_c;)

   126

 * These will not be used in flex, but the token type union defined

   127

 * in iec_bison.hh contains pointers to these classes, so we must include

   128

 * it here.

   129

 */

   130

#include "../absyntax/absyntax.hh"

   131

   132

   133

/* iec_bison.hh is generated by bison.

   134

 * Contains the definition of the token constants, and the

   135

 * token value type YYSTYPE (in our case, a 'const char *')

   136

 */

   137

#include "iec_bison.hh"

   138

#include "stage1_2_priv.hh"

   139

   140

   141

/* Variable defined by the bison parser,

   142

 * where the value of the tokens will be stored

   143

 */

   144

extern YYSTYPE yylval;

   145

   146

/* The name of the file currently being parsed...

   147

 * Note that flex accesses and updates this global variable

   148

 * apropriately whenever it comes across an (*#include <filename> *) directive...

   149

 */

   150

const char *current_filename = NULL;

   151

   152

   153

   154

/* Variable defined by the bison parser.

   155

 * It must be initialised with the location

   156

 * of the token being parsed.

   157

 * This is only needed if we want to keep

   158

 * track of the locations, in order to give

   159

 * more meaningful error messages!

   160

 */

   161

/*

   162

 *extern YYLTYPE yylloc;

   163

b*/

   164

#define YY_INPUT(buf,result,max_size)  {\

   165

    result = GetNextChar(buf, max_size);\

   166

    if (  result <= 0  )\

   167

      result = YY_NULL;\

   168

    }

   169

   170

   171

/* Macro that is executed for every action.

   172

 * We use it to pass the location of the token

   173

 * back to the bison parser...

   174

 */

   175

#define YY_USER_ACTION {\

   176

	yylloc.first_line = current_tracking->lineNumber;			\

   177

	yylloc.first_column = current_tracking->currentTokenStart;		\

   178

	yylloc.first_file = current_filename;					\

   179

	yylloc.first_order = current_order;					\

   180

	yylloc.last_line = current_tracking->lineNumber;			\

   181

	yylloc.last_column = current_tracking->currentChar - 1;			\

   182

	yylloc.last_file = current_filename;					\

   183

	yylloc.last_order = current_order;					\

   184

	current_tracking->currentTokenStart = current_tracking->currentChar;	\

   185

	current_order++;							\

   186

	}

   187

   188

   189

   190

/* Since this lexical parser we defined only works in ASCII based

   191

 * systems, we might as well make sure it is being compiled on

   192

 * one...

   193

 * Lets check a few random characters...

   194

 */

   195

#if (('a' != 0x61) || ('A' != 0x41) || ('z' != 0x7A) || ('Z' != 0x5A) || \

   196

     ('0' != 0x30) || ('9' != 0x39) || ('(' != 0x28) || ('[' != 0x5B))

   197

#error This lexical analyser is not portable to a non ASCII based system.

   198

#endif

   199

   200

   201

/* Function only called from within flex, but defined

   202

 * in iec.y!

   203

 * We declare it here...

   204

 *

   205

 * Search for a symbol in either of the two symbol tables

   206

 * and return the token id of the first symbol found.

   207

 * Searches first in the variables, and only if not found

   208

 * does it continue searching in the library elements

   209

 */

   210

//token_id_t get_identifier_token(const char *identifier_str);

   211

int get_identifier_token(const char *identifier_str);

   212

%}

   213

   214

   215

/***************************************************/

   216

/* Forward Declaration of functions defined later. */

   217

/***************************************************/

   218

   219

%{

   220

/* return all the text in the current token back to the input stream. */

   221

void unput_text(unsigned int n);

   222

/* return all the text in the current token back to the input stream, 

   223

 * but first return to the stream an additional character to mark the end of the token. 

   224

 */

   225

void unput_and_mark(const char c);

   226

   227

void include_file(const char *include_filename);

   228

   229

int GetNextChar(char *b, int maxBuffer);

   230

%}

   231

   232

   233

   234

/****************************/

   235

/* Lexical Parser States... */

   236

/****************************/

   237

   238

/* NOTE: Our psrser can parse st or il code, intermixed

   239

 *       within the same file.

   240

 *       With IL we come across the issue of the EOL (end of line) token.

   241

 *       ST, and the declaration parts of IL do not use this token!

   242

 *       If the lexical analyser were to issue this token during ST

   243

 *       language parsing, or during the declaration of data types,

   244

 *       function headers, etc. in IL, the syntax parser would crash.

   245

 *

   246

 *       We can solve this issue using one of three methods:

   247

 *        (1) Augment all the syntax that does not accept the EOL

   248

 *            token to simply ignore it. This makes the syntax

   249

 *            definition (in iec.y) very cluttered!

   250

 *        (2) Let the lexical parser figure out which language

   251

 *            it is parsing, and decide whether or not to issue

   252

 *            the EOL token. This requires the lexical parser

   253

 *            to have knowledge of the syntax!, making for a poor

   254

 *            overall organisation of the code. It would also make it

   255

 *            very difficult to understand the lexical parser as it

   256

 *            would use several states, and a state machine to transition

   257

 *            between the states. The state transitions would be

   258

 *            intermingled with the lexical parser defintion!

   259

 *        (3) Use a mixture of (1) and (2). The lexical analyser

   260

 *            merely distinguishes between function headers and function

   261

 *            bodies, but no longer makes a distinction between il and

   262

 *            st language bodies. When parsing a body, it will return

   263

 *            the EOL token. In other states '\n' will be ignored as

   264

 *            whitespace.

   265

 *            The ST language syntax has been augmented in the syntax

   266

 *            parser configuration to ignore any EOL tokens that it may

   267

 *            come across!

   268

 *            This option has both drawbacks of option (1) and (2), but

   269

 *            much less intensely.

   270

 *            The syntax that gets cluttered is limited to the ST statements

   271

 *            (which is rather limited, compared to the function headers and

   272

 *            data type declarations, etc...), while the state machine in

   273

 *            the lexical parser becomes very simple. All state transitions

   274

 *            can be handled within the lexical parser by itself, and can be

   275

 *            easily identified. Thus knowledge of the syntax required by

   276

 *            the lexical parser is very limited!

   277

 *

   278

 * Amazingly enough, I (Mario) got to implement option (3)

   279

 * at first, requiring two basic states, decl and body.

   280

 * The lexical parser will enter the body state when

   281

 * it is parsing the body of a function/program/function block. The

   282

 * state transition is done when we find a VAR_END that is not followed

   283

 * by a VAR! This is the syntax knowledge that gets included in the

   284

 * lexical analyser with this option!

   285

 * Unfortunately, getting the st syntax parser to ignore EOL anywhere

   286

 * where they might appear leads to conflicts. This is due to the fact

   287

 * that the syntax parser uses the single look-ahead token to remove

   288

 * possible conflicts. When we insert a possible EOL, the single

   289

 * look ahead token becomes the EOL, which means the potential conflicts

   290

 * could no longer be resolved.

   291

 * Removing these conflicts would make the st syntax parser very convoluted,

   292

 * and adding the extraneous EOL would make it very cluttered.

   293

 * This option was therefore dropped in favour of another!

   294

 *

   295

 * I ended up implementing (2). Unfortunately the lexical analyser can

   296

 * not easily distinguish between il and st code, since function

   297

 * calls in il are very similar to function block calls in st.

   298

 * We therefore use an extra 'body' state. When the lexical parser

   299

 * finds that last END_VAR, it enters the body state. This state

   300

 * must figure out what language is being parsed from the first few

   301

 * tokens, and switch to the correct state (st, il or sfc) according to the

   302

 * language. This means that we insert quite a bit of knowledge of the

   303

 * syntax of the languages into the lexical parser. This is ugly, but it

   304

 * works, and at least it is possible to keep all the state changes together

   305

 * to make it easier to remove them later on if need be.

   306

 * Once the language being parsed has been identified, 

   307

 * the body state returns any matched text back to the buffer with unput(),

   308

 * to be later matched correctly by the apropriate language parser (st, il or sfc).

   309

 *

   310

 * Aditionally, in sfc state it may further recursively enter the body state

   311

 * once again. This is because an sfc body may contain ACTIONS, which are then

   312

 * written in one of the three languages (ST, IL or SFC), so once again we need

   313

 * to figure out which language the ACTION in the SFC was written in. We already

   314

 * ahve all that done in the body state, so we recursively transition to the body 

   315

 * state once again.

   316

 * Note that in this case, when coming out of the st/il state (whichever language

   317

 * the action was written in) the sfc state will become active again. This is done by

   318

 * pushing and poping the previously active state!

   319

 *

   320

 * The sfc_qualifier_state is required because when parsing actions within an

   321

 * sfc, we will be expecting action qualifiers (N, P, R, S, DS, SD, ...). In order

   322

 * to bison to work correctly, these qualifiers must be returned as tokens. However,

   323

 * these tokens are not reserved keywords, which means it should be possible to

   324

 * define variables/functions/FBs with any of these names (including 

   325

 * S and R which are special because they are also IL operators). So, when we are not

   326

 * expecting any action qualifiers, flex does not return these tokens, and is free

   327

 * to interpret them as previously defined variables/functions/... as the case may be.

   328

 *

   329

 * The time_literal_state is required because TIME# literals are decomposed into 

   330

 * portions, and wewant to send these portions one by one to bison. Each poertion will 

   331

 * represent the value in days/hours/minutes/seconds/ms.

   332

 * Unfortunately, some of these portions may also be lexically analysed as an identifier. So,

   333

 * we need to disable lexical identification of identifiers while parsing TIME# literals!

   334

 * e.g.:  TIME#55d_4h_56m

   335

 *       We would like to return to bison the tokens 'TIME' '#' '55d' '_' '4h' '_' '56m'

   336

 *       Unfortunately, flex will join '_' and '4h' to create a legal {identifier} '_4h',

   337

 *       and return that identifier instead! So, we added this state!

   338

 *

   339

 * The ignore_pou_state state is only used when bison says it is doing the pre-parsing.

   340

 * During pre-parsing, the main state machine will only transition between

   341

 * INITIAL and ignore_pou_state, and from here back to INITIAL. All other

   342

 * transitions are inhibited. This inhibition is actually just enforced by making

   343

 * sure that the INITIAL ---> ignore_pou_state transition is tested before all other

   344

 * transitions coming out of INITIAL state. All other transitions are unaffected, as they

   345

 * never get a chance to be evaluated when bison is doing pre-parsing.

   346

 * Pre-parsing is a first quick scan through the whole input source code simply

   347

 * to determine the list of POUs and datatypes that will be defined in that

   348

 * code. Basically, the objective is to fill up the previously_declared_xxxxx

   349

 * maps, without processing the code itself. Once these maps have been filled up,

   350

 * bison will throw away the AST (abstract syntax tree) created up to that point, 

   351

 * and scan through the same source code again, but this time creating a correct AST.

   352

 * This pre-scan allows the source code to reference POUs and datatypes that are

   353

 * only declared after they are used!

   354

 * 

   355

 *

   356

 * Here is a main state machine...

   357

 *                                                                         --+  

   358

 *                                                                           |  these states are

   359

 *              +------------> get_pou_name_state  ----> ignore_pou_state    |  only active 

   360

 *              |                                            |               |  when bison is 

   361

 *              |  ------------------------------------------+               |  doing the 

   362

 *              |  |                                                         |  pre-parsing!!

   363

 *              |  v                                                       --+

   364

 *       +---> INITIAL <-------> config

   365

 *       |        \

   366

 *       |        V

   367

 *       |   header_state

   368

 *       |        |

   369

 *       |        V

   370

 *     vardecl_list_state <------> var_decl

   371

 *       ^        | 

   372

 *       |        | [using push()]

   373

 *       |        |

   374

 *       |        V

   375

 *       |       body, 

   376

 *       |        |

   377

 *       |        | 

   378

 *       |   -------------------

   379

 *       |   |       |         |

   380

 *       |   v       v         v

   381

 *       |  st      il        sfc

   382

 *       |   |       |         |  [using pop() when leaving st/il/sfc => goes to vardecl_list_state]

   383

 *       |   |       |         |

   384

 *       -----------------------

   385

 *

   386

 * NOTE:- When inside sfc, and an action or transition in ST/IL is found, then 

   387

 *        we also push() to the body state. This means that sometimes, when pop()ing

   388

 *        from st and il, the state machine may return to the sfc state!

   389

 *      - The transitions form sfc to body will be decided by bison, which will

   390

 *        tell flex to do the transition by calling cmd_goto_body_state().

   391

 *   

   392

 * 

   393

 * Possible state changes are:

   394

 *   INITIAL -> goto(ignore_pou_state)

   395

 *               (This transition state is only used when bison says it is doing the pre-parsing.)

   396

 *               (This transition takes precedence over all other transitions!)

   397

 *               (when a FUNCTION, FUNCTION_BLOCK, PROGRAM or CONFIGURATION is found)

   398

 * 

   399

 *   INITIAL -> goto(config_state)

   400

 *                (when a CONFIGURATION is found)

   401

 * 

   402

 *   INITIAL -> goto(header_state)

   403

 *               (when a FUNCTION, FUNCTION_BLOCK, or PROGRAM is found)

   404

 * 

   405

 *   header_state -> goto(vardecl_list_state)

   406

 *               (When the first VAR token is found, i.e. at begining of first VAR .. END_VAR declaration)

   407

 * 

   408

 *  vardecl_list_state -> push current state (vardecl_list_state), and goto(vardecl_state) 

   409

 *                (when a VAR token is found)

   410

 *   vardecl_state -> pop() to (vardecl_list_state) 

   411

 *                (when a END_VAR token is found)

   412

 * 

   413

 *   vardecl_list_state -> push current state (vardecl_list_state), and goto(body_state) 

   414

 *                (when the last END_VAR is found!)

   415

 *

   416

 *   body_state    -> goto(sfc_state)

   417

 *                     (when it figures out it is parsing sfc language)

   418

 *   body_state    -> goto(st_state)

   419

 *                     (when it figures out it is parsing st language)

   420

 *   body_state    -> goto(il_state)

   421

 *                     (when it figures out it is parsing il language)

   422

 *   st_state      -> pop() to vardecl_list_state

   423

 *                     (when a END_FUNCTION, END_FUNCTION_BLOCK, END_PROGRAM,

   424

 *                      END_ACTION or END_TRANSITION is found)

   425

 *   il_state      -> pop() to vardecl_list_state

   426

 *                     (when a END_FUNCTION, END_FUNCTION_BLOCK, END_PROGRAM,

   427

 *                      END_ACTION or END_TRANSITION is found)

   428

 *   sfc_state     -> pop() to vardecl_list_state

   429

 *                     (when a END_FUNCTION, END_FUNCTION_BLOCK, or END_PROGRAM is found)

   430

 * 

   431

 *   ignore_pou_state   -> goto(INITIAL)

   432

 *                         (when a END_FUNCTION, END_FUNCTION_BLOCK, END_PROGRAM or END_CONFIGURATION is found)

   433

 *   vardecl_list_state -> goto(INITIAL)

   434

 *                         (when a END_FUNCTION, END_FUNCTION_BLOCK, or END_PROGRAM is found)

   435

 *   config_state       -> goto(INITIAL)

   436

 *                         (when a END_CONFIGURATION is found)

   437

 * 

   438

 *  

   439

 *   sfc_state     -> push current state(sfc_state); goto(body_state)

   440

 *                     (when parsing an action. This transition is requested by bison)

   441

 *   sfc_state     -> push current state(sfc_state); goto(sfc_qualifier_state)

   442

 *                     (when expecting an action qualifier. This transition is requested by bison)

   443

 *   sfc_qualifier_state -> pop() to sfc_state

   444

 *                     (when no longer expecting an action qualifier. This transition is requested by bison)

   445

 *

   446

 *   config_state  -> push(config_state); goto(task_init_state)

   447

 *                     (when parsing a task initialisation. This transition is requested by bison)

   448

 *   task_init_state -> pop()

   449

 *                     (when no longer parsing task initialisation parameters. This transition is requested by bison)

   450

 *

   451

 * 

   452

 * There is another secondary state machine for parsing comments, another for file_includes, 

   453

 * and yet another for time literals.

   454

 */

   455

   456

   457

/* Bison is in the pre-parsing stage, and we are parsing a POU. Ignore everything up to the end of the POU! */

   458

%x ignore_pou_state

   459

%x get_pou_name_state

   460

   461

/* we are parsing a configuration. */

   462

%s config_state

   463

   464

/* Inside a configuration, we are parsing a task initialisation parameters */

   465

/* This means that PRIORITY, SINGLE and INTERVAL must be handled as

   466

 * tokens, and not as possible identifiers. Note that the above words

   467

 * are not keywords.

   468

 */

   469

%s task_init_state

   470

   471

/* we are looking for the first VAR inside a function's, program's or function block's declaration */

   472

/* This is not exclusive (%x) as we must be able to parse the identifier and data types of a function/FB */

   473

%s header_state

   474

   475

/* we are parsing a function, program or function block sequence of VAR..END_VAR delcarations */

   476

%x vardecl_list_state 

   477

/* a substate of the vardecl_list_state: we are inside a specific VAR .. END_VAR */

   478

%s vardecl_state

   479

   480

/* we will be parsing a function body/action/transition. Whether il/st/sfc remains to be determined */

   481

%x body_state

   482

   483

/* we are parsing il code -> flex must return the EOL tokens!       */

   484

%s il_state

   485

   486

/* we are parsing st code -> flex must not return the EOL tokens!   */

   487

%s st_state

   488

   489

/* we are parsing sfc code -> flex must not return the EOL tokens!  */

   490

%s sfc_state

   491

   492

/* we are parsing sfc code, and expecting an action qualifier.      */

   493

%s sfc_qualifier_state

   494

   495

/* we are parsing sfc code, and expecting the priority token.       */

   496

%s sfc_priority_state

   497

   498

/* we are parsing a TIME# literal. We must not return any {identifier} tokens. */

   499

%x time_literal_state

   500

   501

/* we are parsing a comment. */

   502

%x comment_state

   503

   504

   505

/*******************/