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.h contains pointers to these classes, so we must include

   128

 * it here.

   129

 */

   130

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

   131

   132

   133

/* iec_bison.h 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.h"

   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

/* We will not be using unput() in our flex code... */

   155

/* NOTE: it seems that this #define is no longer needed, It has been 

   156

 * replaced by %option nounput.

   157

 * Should we simply delete it?

   158

 * For now leave it in, in case someone is using an old version of flex.

   159

 * In any case, the most harm that can result in a warning message

   160

 * when compiling iec.flex.c:

   161

 * warning: ‘void yyunput(int, char*)’ defined but not used

   162

 */

   163

#define YY_NO_UNPUT

   164

   165

/* Variable defined by the bison parser.

   166

 * It must be initialised with the location

   167

 * of the token being parsed.

   168

 * This is only needed if we want to keep

   169

 * track of the locations, in order to give

   170

 * more meaningful error messages!

   171

 */

   172

/*

   173

 *extern YYLTYPE yylloc;

   174

b*/

   175

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

   176

    result = GetNextChar(buf, max_size);\

   177

    if (  result <= 0  )\

   178

      result = YY_NULL;\

   179

    }

   180

   181

   182

/* Macro that is executed for every action.

   183

 * We use it to pass the location of the token

   184

 * back to the bison parser...

   185

 */

   186

#define YY_USER_ACTION {\

   187

	yylloc.first_line = current_tracking->lineNumber;			\

   188

	yylloc.first_column = current_tracking->currentTokenStart;		\

   189

	yylloc.first_file = current_filename;					\

   190

	yylloc.first_order = current_order;					\

   191

	yylloc.last_line = current_tracking->lineNumber;			\

   192

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

   193

	yylloc.last_file = current_filename;					\

   194

	yylloc.last_order = current_order;					\

   195

	current_tracking->currentTokenStart = current_tracking->currentChar;	\

   196

	current_order++;							\

   197

	}

   198

   199

   200

   201

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

   202

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

   203

 * one...

   204

 * Lets check a few random characters...

   205

 */

   206

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

   207

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

   208

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

   209

#endif

   210

   211

   212

/* Function only called from within flex, but defined

   213

 * in iec.y!

   214

 * We declare it here...

   215

 *

   216

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

   217

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

   218

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

   219

 * does it continue searching in the library elements

   220

 */

   221

//token_id_t get_identifier_token(const char *identifier_str);

   222

int get_identifier_token(const char *identifier_str);

   223

%}

   224

   225

   226

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

   227

/* Forward Declaration of functions defined later. */

   228

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

   229

   230

%{

   231

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

   232

void unput_text(unsigned int n);

   233

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

   234

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

   235

 */

   236

void unput_and_mark(const char c);

   237

   238

void include_file(const char *include_filename);

   239

   240

int GetNextChar(char *b, int maxBuffer);

   241

%}

   242

   243

   244

   245

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

   246

/* Lexical Parser States... */

   247

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

   248

   249

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

   250

 *       within the same file.

   251

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

   252

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

   253

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

   254

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

   255

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

   256

 *

   257

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

   258

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

   259

 *            token to simply ignore it. This makes the syntax

   260

 *            definition (in iec.y) very cluttered!

   261

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

   262

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

   263

 *            the EOL token. This requires the lexical parser

   264

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

   265

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

   266

 *            very difficult to understand the lexical parser as it

   267

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

   268

 *            between the states. The state transitions would be

   269

 *            intermingled with the lexical parser defintion!

   270

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

   271

 *            merely distinguishes between function headers and function

   272

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

   273

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

   274

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

   275

 *            whitespace.

   276

 *            The ST language syntax has been augmented in the syntax

   277

 *            parser configuration to ignore any EOL tokens that it may

   278

 *            come across!

   279

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

   280

 *            much less intensely.

   281

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

   282

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

   283

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

   284

 *            the lexical parser becomes very simple. All state transitions

   285

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

   286

 *            easily identified. Thus knowledge of the syntax required by

   287

 *            the lexical parser is very limited!

   288

 *

   289

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

   290

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

   291

 * The lexical parser will enter the body state when

   292

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

   293

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

   294

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

   295

 * lexical analyser with this option!

   296

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

   297

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

   298

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

   299

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

   300

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

   301

 * could no longer be resolved.

   302

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

   303

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

   304

 * This option was therefore dropped in favour of another!

   305

 *

   306

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

   307

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

   308

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

   309

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

   310

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

   311

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

   312

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

   313

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

   314

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

   315

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

   316

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

   317

 * Once the language being parsed has been identified, 

   318

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

   319

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

   320

 *

   321

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

   322

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

   323

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

   324

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

   325

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

   326

 * state once again.

   327

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

   328

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

   329

 * pushing and poping the previously active state!

   330

 *

   331

 * The sfc_qualifier_state is required because when parsing actions within an

   332

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

   333

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

   334

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

   335

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

   336

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

   337

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

   338

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

   339

 *

   340

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

   341

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

   342

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

   343

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

   344

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

   345

 * e.g.:  TIME#55d_4h_56m

   346

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

   347

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

   348

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

   349

 *

   350

 * There is a main state machine...

   351

 * 

   352

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

   353

 *       |        \

   354

 *       |        V

   355

 *       |   header_state

   356

 *       |        |

   357

 *       |        V

   358

 *     vardecl_list_state <------> var_decl

   359

 *       ^        | 

   360

 *       |        | [using push()]

   361

 *       |        |

   362

 *       |        V

   363

 *       |       body, 

   364

 *       |        |

   365

 *       |        | 

   366

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

   367

 *       |   |       |         |

   368

 *       |   v       v         v

   369

 *       |  st      il        sfc

   370

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

   371

 *       |   |       |         |

   372

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

   373

 *

   374

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

   375

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

   376

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

   377

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

   378

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

   379

 *   

   380

 * 

   381

 * Possible state changes are:

   382

 *   INITIAL -> goto(config_state)

   383

 *                (when a CONFIGURATION is found)

   384

 * 

   385

 *   INITIAL -> goto(header_state)

   386

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

   387

 *   header_state -> goto(vardecl_list_state)

   388

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

   389

 * 

   390

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

   391

 *                (when a VAR token is found)

   392

 *   vardecl_state -> pop() to (vardecl_list_state) 

   393

 *                (when a END_VAR token is found)

   394

 * 

   395

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

   396

 *                (when the last END_VAR is found!)

   397

 *

   398

 *   body_state    -> goto(sfc_state)

   399

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

   400

 *   body_state    -> goto(st_state)

   401

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

   402

 *   body_state    -> goto(il_state)

   403

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

   404

 *   st_state      -> pop() to vardecl_list_state

   405

 *                     (when a END_FUNCTION, END_FUNCTION_BLOCK, END_PROGRAM,

   406

 *                      END_ACTION or END_TRANSITION is found)

   407

 *   il_state      -> pop() to vardecl_list_state

   408

 *                     (when a END_FUNCTION, END_FUNCTION_BLOCK, END_PROGRAM,

   409

 *                      END_ACTION or END_TRANSITION is found)

   410

 *   sfc_state     -> pop() to vardecl_list_state

   411

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

   412

 * 

   413

 *   vardecl_list_state -> goto(INITIAL)

   414

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

   415

 *   config_state  -> goto(INITIAL)

   416

 *                     (when a END_CONFIGURATION is found)

   417

 * 

   418

 *  

   419

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

   420

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

   421

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

   422

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

   423

 *   sfc_qualifier_state -> pop() to sfc_state

   424

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

   425

 *

   426

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

   427

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

   428

 *   task_init_state -> pop()

   429

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

   430

 *

   431

 * 

   432

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

   433

 * and yet another for time literals.

   434

 */

   435

   436

   437

/* we are parsing a configuration. */

   438

%s config_state

   439

   440

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

   441

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

   442

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

   443

 * are not keywords.

   444

 */

   445

%s task_init_state

   446

   447

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

   448

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

   449

%s header_state

   450

   451

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

   452

%x vardecl_list_state 

   453

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

   454

%s vardecl_state

   455

   456

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

   457

%x body_state

   458

   459

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

   460

%s il_state

   461

   462

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

   463

%s st_state

   464

   465

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

   466

%s sfc_state

   467

   468

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

   469

%s sfc_qualifier_state

   470

   471

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

   472

%s sfc_priority_state

   473

   474

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

   475

%x time_literal_state

   476

   477

/* we are parsing a comment. */

   478

%x comment_state

   479

   480

   481

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

   482

/* File #include's */

   483

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

   484

   485

/* We extend the IEC 61131-3 standard syntax to allow inclusion

   486

 * of other files, using the IEC 61131-3 pragma directive...

   487

 * The accepted syntax is:

   488

 *  {#include "<filename>"}

   489

 */

   490

   491

/* the "include" states are used for picking up the name of an include file */

   492

%x include_beg

   493

%x include_filename

   494

%x include_end

   495

   496

   497

file_include_pragma_filename	[^\"]*

   498

file_include_pragma_beg		"{#include"{st_whitespace}\"

   499

file_include_pragma_end		\"{st_whitespace}"}"

   500

file_include_pragma			{file_include_pragma_beg}{file_include_pragma_filename}{file_include_pragma_end}

   501

   502

   503

%{

   504

   505

/* A counter to track the order by which each token is processed.

   506

 * NOTE: This counter is not exactly linear (i.e., it does not get incremented by 1 for each token).

   507

 *       i.e.. it may get incremented by more than one between two consecutive tokens.