Compiler badly detecting badly defined string

8 views
Skip to first unread message

Carlo Hogeveen

unread,
Feb 22, 2026, 5:07:33 AMFeb 22
to sem...@googlegroups.com

This is an insignificant macro programming problem.
If a string is defined with an "=" operator and without a value, then the compiler reports an unrelated problem sometimes many lines lower and sometimes for an unrelated statement.
The macro below demonstrates this.
The badly defined string did not happen in one of my macros of course; I was testing for a friend.

Carlo


proc Main()
integer i = 0
string s [MAXSTRINGLEN] =

i = 1
i = 2
i = 3

if s == ''
i = i + 1
endif

PurgeMacro(CurrMacroFilename())
end Main





Reply all
Reply to author
Forward
0 new messages