Configurable black list on specific statements

[SLabuz95]

Initial idea

Black list to catch specific statements. User should fill black list in configuration.

In case of occurence of black list's statement, few actions shall be possible:

• set mark in code (// BLS)
• rule defined by user
• user defined error

[SLabuz95]

Introduction

In some cases, complex computations are required to correctly translate text. For example, different amount of text shall be ignored before and after occurance of specific event.

In that case, user would fix generated text by hand.

To help a user in this task, application allows user to call executable action in the rule to mark text, which should be changed by hand.

Current concept

In the application, user can mark the text, which should be changed by hand with the following features:

• in an interpreter configuration, user can toogle an option UserInteraction = <Required / NotRequired> for any procedure name to generate mark for any occurance of the procedure call with the procedure name,
• user can define the rule, which will generate any mark for example by Write action , AddPreexpression action or Error action.

Upgrade Request

Description

Black list is a feature, which allows to specify strings. In case of occurence of the black list's string as a substring of procedure call name or arguments of the procedure call, procedure call will be ignored and special mark will be generated to inform user about it.

Input

Strings for the black list will be temporarely specified in the Definitions List of Instance Configuration Panel. For no Definitions List have no rule in text generating, cause of regress in Variables Recognition System of the interpreter. Definitions List will be moved to Inputs List with new functionality: Virtual Outputs List #27.

---

Reason

User receives specialized feature, which do not require to think about creating the rules for specific procedure names. User doesnt need to check and analyse all rules to verify, which of all strings are already blacklisted.

Verdict

Approved

Reason

Simplify the process of marking text, which should be modified by hand.

State

In development.

Implementation plan

1. Specify, which states can cause the issue at procedure for sign #.
2. Develop an alogithm:
3. Add variables (list of strings - blacklisted strings + boolean flag - type of reaction on an event + mark string) to configuration class.
4. Modify definitions list in the input panel to take and control black listed string. Additionally line edit for mark generated by interpreter and check box to choose type of reaction on an event.
5. Integrate black list panel with configuration (prepare configuration on generation startup).

Implementation details

1. List of states:

2. Algorithm:

3. New variables: