SAPIEN Forums

Product: PrimalScript (64 Bit)
Build: v7.4.120
OS: Windows 10 Pro (64 Bit)
Build: v10.0.16299

At least one Unicode character that we have used in our scripts for many years causes the 2019 version to stop reading the script file, sometimes with gibberish after the character. The 2018 and 2014 versions read everything just fine.

The right double arrow is particularly troublesome:
" » "
In a comment it seems to simply stop reading the script. In code it causes the odd error you will find in the attached file, as well as an error that some lines are over 8128 characters long (they are NOT).
Thanks,

Gerald Michaud
gmichaud@dxc.com

BTW, the dropdown on this web page to "select code" type doesn't seem to have a selection for vbscript. We make a LOT of vbscripts. Hopefully some day we'll move to powershell, but for the foreseeable future it's all vbscript.

Thanks for reporting the issue.
The issue has been sent to the proper place for evaluation and correction. When a fix is issued with a service build, it will be listed in the change log.

It's fixed and in QA. There is new code to detect BOMs (Byte Order Marks) mid file because some folks started to concatenate unicode files with the good old DOS copy command. That created problems as you might imagine. The detection code was flawed though, so that caused your problem. Thought maybe you are curious

Thanks for the quick resolution and extra info. I DO like to hear these details.

One thing I learned a long time ago is that no matter how hard you try to think of all the usage scenarios and all possible ways users can break something, they'll still surprise you!

Any idea how long this will remain in QA? I'd like to provide an ETA to the rest or our team.

Thanks,
Gerry

Not sure at the moment. There are few other changes in that build that still require some work. I will know more after today.

The fix has been released in the latest service build (7.4.121).

thanks. i'll test it this morning.