Compare commits

...

1 Commits

Author SHA1 Message Date
Irmen de Jong
5cb8bcead7 todo 2025-08-03 00:54:43 +02:00
2 changed files with 3 additions and 2 deletions

View File

@@ -2346,7 +2346,7 @@ internal class AstChecker(private val program: Program,
return value.type==BaseDataType.UWORD
}
targetDt.isStructInstance -> {
return err("assigning this value to struct instance not supported (use pointers)")
return err("assigning this value to struct instance not supported")
}
else -> return err("value type ${value.type.toString().lowercase()} doesn't match target type $targetDt")
}
@@ -2470,7 +2470,7 @@ internal class AstChecker(private val program: Program,
if(sourceDatatype.isStructInstance && sourceDatatype != targetDatatype)
errors.err("value type $sourceDatatype doesn't match target type $targetDatatype", position)
else
errors.err("assigning this value to struct instance not supported (use pointers)", position)
errors.err("assigning this value to struct instance not supported", position)
}
else
errors.err("value type $sourceDatatype doesn't match target type $targetDatatype", position)

View File

@@ -88,6 +88,7 @@ STRUCTS and TYPED POINTERS
Future Things and Ideas
^^^^^^^^^^^^^^^^^^^^^^^
- %breakpoint after an assignment is parsed as part of the expression (x % breakpoint), that should not happen
- when a complete block is removed because unused, suppress all info messages about everything in the block being removed
- fix the line, cols in Position, sometimes they count from 0 sometimes from 1
- is "checkAssignmentCompatible" redundant (gets called just 1 time!) when we also have "checkValueTypeAndRange" ?