error 21: Internal!, HMEMBERID

[CanMetax]

Hello,

Code: Select all

enum colors
		RED= 1
		GREEN
		BLUE
end enum

type _colors as colors

type foo

	type farbe as _colors

private:
	as ubyte nop= -1
end type

dim as foo bar
bar.farbe= GREEN

[fxm]

type farbe as _colors
farbe as _colors
or
dim farbe as _colors

[CanMetax]

yes the declaration is nonsense.
doesn't this error message indicate a compiler error?

[fxm]

Hello,

Code: Select all

enum colors
		RED= 1
		GREEN
		BLUE
end enum

type _colors as colors

type foo

	type farbe as _colors

private:
	as ubyte nop= -1
end type

dim as foo bar
bar.farbe= GREEN

With the last freeBASIC compiler version (under testing) which allows the Nested Types (I suppose you use it), this declaration ('type farbe as _colors') is a Type (Alias) declaration nested in the 'foo' Type (UDT), which is valid.
Your code is valid up to:
'bar.farbe= GREEN'
Here, I think this detected internal error is not the one to report to user and must be modified.

Simple example of bugged error message:

Code: Select all

Type UDT
    Dim As Integer I
    Type Int_ As Long
End Type

Dim As UDT u
u.Int_ = 0

C:\.....\FBIDETEMP.bas(7) error 21: Internal!, HMEMBERID in 'u.Int_ = 0'

[coderJeff]

Hello,

Thanks for the feedback.

Yes, the new feature with nested named types basically adds TYPE-NAME as a new kind of member that never existed before. I actually thought I looked at this case before, but I guess is something we missed. Ah, didn't look at this since adding some capabilities with the type alias's (typedef's).
---
@fxm, I seen your cases for the new feature and bug report. I will try to get on it soon.

[coderJeff]

Here, I think this detected internal error is not the one to report to user and must be modified.

I pushed changed to fbc/master to fix this.

I didn't update the changelog.txt for this specifically. I know we talked about this before, but I don't know, it's a change to a feature currently in active development seems irrelevant to differences from previous fbc 1.09.0 version.