mirror of
https://github.com/ultimatepp/ultimatepp.git
synced 2026-05-15 14:16:07 -06:00
[GH-ISSUE #162] TheIDE windows version shows parsing errors #70
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/ultimatepp#70
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @erusyd on GitHub (Aug 29, 2023).
Original GitHub issue: https://github.com/ultimatepp/ultimatepp/issues/162
Originally assigned to: @erusyd on GitHub.
I downloaded Protect package from:


https://www.ultimatepp.org/forums/index.php?t=rview&th=5547&goto=49922
When I open "ProtectEncrypt" from linux, parsing is OK:
But when I open it from Windows 10 Enterprise LTSC in vmware workstation, it shows parsing errors:
I've attached the source files(put "Protect" and "Xed" in uppsrc, and "ProctecEncrypt" in MyApps):
ProtectPackage.zip
@mirek-fidler commented on GitHub (Sep 5, 2023):
This might be fixed in the current master, please check.
@erusyd commented on GitHub (Sep 6, 2023):
Problem still exists:

@mirek-fidler commented on GitHub (Sep 6, 2023):
If you activate Assist diagnostics in Settings/Assist, there should be
"Current file parse errors" in Assist menu. Can you dump that list here?
Also, looking at the screenshot, it feels like it is possibly actual error.
If it is not "private" code, can you send me "ProtectEncrypt"?
On Wed, Sep 6, 2023 at 7:41 AM Song Yadong @.***> wrote:
@erusyd commented on GitHub (Sep 6, 2023):
Everything is in the zip. Put "Protect" and "Xed" in uppsrc, and "ProctecEncrypt" in MyApps:
ProtectPackage.zip
@erusyd commented on GitHub (Sep 6, 2023):
parse_errors.txt
@mirek-fidler commented on GitHub (Sep 6, 2023):
Well, it does not build either. The problem is in Xed - VERSION file
conflicts with standard library version file. Renaming VERSION to VERSION0
fixes both build and Assist.
On Wed, Sep 6, 2023 at 12:06 PM Song Yadong @.***>
wrote:
@erusyd commented on GitHub (Sep 7, 2023):
Thanks. MSVC17 compiler is OK with VERSION file. I'm just wondering why Linux does not have such problem.
@mirek-fidler commented on GitHub (Sep 7, 2023):
Linux: "VERSION" vs "version" I think - win32 is case insensitive.
All that said, maybe assist handling of internal includes is not quite
correct - I put that dir at the end of include path...
Mirek
On Thu, Sep 7, 2023 at 2:46 AM Song Yadong @.***> wrote:
@erusyd commented on GitHub (Sep 7, 2023):
OK, clear now.