struc (lbl) assign? var*
        lbl = var
end struc
    

struc assign? var*
        . = var
end struc    

myvar assign 3        ; Here "myvar" is a label to the labeled instruction "assign"

assert myvar = 3    

"struc" itself is not a labeled instruction but a built-in fasmg
command...

..."struc" is categorized as a command...

...lets you define your own labeled instructions...

...the instruction "some".

So that means first identifier can be either in the instruction category or command category. Does fasmg allow other categories for first identifier?

Do we have a reference list of predefined fasmg instructions and commands and any other identifier type that can be used as first identifier? Is this a reasonable approach to understanding what's involved in defining a labeled instruction?

Question #2:
In the term "labeled instruction" What does "labeled" mean? Based on your example, "assign", if you're saying that "struc" is not a label (I do understand that "struc" is a command), then I can understand that. So does labeled instruction mean an instruction that can be labeled? If so, then I suggest clarify that in the documentation because the term "labeled instruction" is easily misinterpreted to mean that the label is specified as the instruction is defined.

lbl: db $FF    

lbl db $FF    

macro dc.b val*
    db val
end macro

struc dc.b val*
    .:
    db val
end struc    

some_label dc.b $FF    

Question #4:
Can a labeled instruction ever be used without a label?

struc lbl_instr val*
    ; something
end struc    

lbl_instr $FF    

Based on your example, "assign", if you're saying that "struc" is not a label (I do understand that "struc" is a command), then I can understand that.

macro dc.b val*
    db val
end macro

struc dc.b val*
    .:
    db val
end struc    

some_label dc.b $FF    

...instruction refers to a symbol that belongs to an instruction class, while a command is a complete construct (a sentence,...

When a symbol is defined with a "=" command, ...

...instruction...recognized only when it is the first identifier of the command...

If we treat "=" as a special kind of identifier, it may serve as an example of labeled instruction.

...when the first identifier of the command is not an instruction - in such case the first identifier becomes a label...

A labeled instruction is evaluated when the first identifier of a command is not an instruction and the second identifier is of the labeled instruction class:

macro try line&
end macro

struc try line&
        .: try line ; create the label, invoke the macro
end struc    

Is the symbol the argument of an expression?
YES:
    Finished
NO:
    Is the symbol a command/instruction?
    YES:
        Finished
    NO:
        The symbol is a label    

Commands/Directives/Instructions are a process whereas labels and symbols are typically valued. Many instructions are the first word on a line, some instruction can work in a labeled form - as the second word of a line, and others operate in both capacities. The labeled form is invoked when the first word is not identified as an instruction.

The labeled form is invoked when the first word is not identified as an instruction.

The first identifier is not a label if it's an argument to command, correct? E.g. as in "x = 1"? See my flowchart, for example.

struc pow?: n,e ; exponentiation, n^e
        repeat 1,dn:n,de:e
                if de > 0
                        local t
                        t pow dn,de shr 1
                        if de and 1
                                . = t * t * dn
                        else
                                . = t * t
                        end if
                else if de = 0
                        . = 1
                else
                        err
                end if
        end repeat
end struc    

I think that a flowchart for parsing the first identifier of a fasmg statement would be something like this:

Code:

Is the symbol the argument of an expression?
YES:
    Finished
NO:
    Is the symbol a command/instruction?
    YES:
        Finished
    NO:
        The symbol is a label    

Why not simply ask," Is the symbol is executable?" Which returns: yes, no, don't know.

If the first identifier is an instruction...

If the first identifier is an instruction it will get executed and '=' becames the start of the first argument.

'=' is not always a command?

macro look_at_this args&
        display "'look_at_this' is called with args:      ", `args, 13
end macro

look_at_this = 3      ; This is not an assignment but a macro call! 'look_at_this' gets called with '= 3' as an argument

purge look_at_this

look_at_this = 1      ; This is not a macro call but an assignment!    

Code:

macro look_at_this args&
        display "'look_at_this' is called with args:      ", `args, 13
end macro

look_at_this = 3      ; This is not an assignment but a macro call! 'look_at_this' gets called with '= 3' as an argument

    

bitRAKE wrote:

If the first identifier is an instruction...

By "instruction", you mean "executable/process" as you have defined in this thread?

"=" may serve as an example of labeled instruction...