Release Candidate for version 13.00 is now available

[alderman2]

I agree with everyone else about the return. We have been worried! 

[TimoVJL]

Project properties for linker don't have LARGEADDRESSAWARE:NO advanced option

To avoid that

Code Select Expand

.drectve SEGMENT
db "-largeaddressaware:no "
.drectve ENDS


[Vortex]

Hi Timo,

Working on your example, I am receiving an error message :

Code Select Expand

;hello64x2.asm

includelib "kernel32.lib"

tp_ExitProcess typedef proto :dword
externdef __imp_ExitProcess : ptr tp_ExitProcess
ExitProcess equ <__imp_ExitProcess>

.drectve SEGMENT
db "-largeaddressaware:no "
.drectve ENDS

.code

mainCRTStartup PROC

    sub rsp, 28h
    invoke ExitProcess, 0

mainCRTStartup ENDP

END

Code Select Expand

E:\PellesC\sample>\PellesC\bin\poasm.exe /AAMD64 Test.asm
E:\PellesC\sample\Test.asm(22): fatal error: Error reading from file 'E:\PellesC\sample\Test.asm'.
The source code is a plain ANSI text file. Poasm Version : 13.00.1

[Pelle]

Project properties for linker don't have LARGEADDRESSAWARE:NO advanced option

Yeah, I guess. A bit of work though with multiple (translation) dialogs, help-file, and revised logic. Will take some time...

[Vortex]

Hello,

About the error message :

Code Select Expand

E:\PellesC\sample\Test.asm(22): fatal error: Error reading from file 'E:\PellesC\sample\Test.asm'.
Adding a blank line after the END statement is solving the issue.

[Pelle]

Hello,

About the error message :

Code Select Expand

E:\PellesC\sample\Test.asm(22): fatal error: Error reading from file 'E:\PellesC\sample\Test.asm'.
Adding a blank line after the END statement is solving the issue.

You get this error when the last line is not properly terminated (no line-break).
Producing a better diagnostic would mean special handling, and more code. This seems silly considering it's uncommon, usually only happening with files from (very) old editors.

[Bitbeisser]

Thanks Pelle!

Glad to see that things are still moving.
I don't use C as much anymore as I used to, but I have over the last decade or so send a lot of folks to this compiler, as it makes programming in plain C so much easier for most newbies than having to deal with the bloated corpses of Visual Studio or GCC...

Ralf

[CandCPlusPlus]

My interest has certainly gone down a bit in recent years. I wanted to finish the C23 version, since I hate leaving projects unfinished, but it's hard to be interested in "C2Y" (the next C standard). We don't even have much of "Wintel" anymore, so I'm not sure where to focus now...

If you decide not to continue updating on Pelles C at some point in the future (or Pelles C 13.0 is the final update you work on), could you make it open source?

Pelles C works well and it doesn't need constant new features. The biggest problem I see happening is future releases of Windows breaking Pelles C because of one reason or another. It's already becoming a problem. Microsoft's support for Windows 10 is ending in October and Windows 11 will be needed for official support from Microsoft.

Edit: Windows 11 Version 24H2 can be tested from within virtual machines using VirtualBox and VMware.

There are several parts of the C23 standard that I find useful but the vast majority of it isn't relevant or interesting to me. The #embed feature is interesting for example.

[Pelle]

If you decide not to continue updating on Pelles C at some point in the future (or Pelles C 13.0 is the final update you work on), could you make it open source?

Unlikely.

It's already becoming a problem. Microsoft's support for Windows 10 is ending in October and Windows 11 will be needed for official support from Microsoft.

Not my problem.

Edit: Windows 11 Version 24H2 can be tested from within virtual machines using VirtualBox and VMware.

Emulation is emulation. Never the real thing.

[TimoVJL]

polib don't like UTF8 def-files, have to change to ANSI format.

[John Z]

In version 12 I use the load last project option.  So when the IDE starts it loads the last project and all source files that were showing in the IDE Editor as a tab are showing just as they were when it was closed.

In version 13 the load last project option is checked and the last project is loaded. However the source files that were open in the Editor when the IDE was last closed are not being opened and showing in the IDE editor as they were when closed.

Have I missed checking an option or is this intentional behavior, or heaven forbid a bug?

John Z

[Pelle]

Have I missed checking an option or is this intentional behavior, or heaven forbid a bug?

Looks like a bug, but I can't find any significant changes in this area since early 2020...

[TimoVJL]

if *.ppx file have a locking problem, what happens ?

EDIT: delete .ppx and close project, after that are files listed in that xml-file normally ?

An example for test code:

Code Select Expand

#define WIN32_LEAN_AND_MEAN
#include <windows.h>
#include <stdio.h>

int __cdecl main(void)
{
HANDLE hDir;
DWORD dwRC;
PFILE_NOTIFY_INFORMATION pfni;
WCHAR fni[(sizeof(FILE_NOTIFY_INFORMATION)+1024)*1];
hDir = CreateFile(".\\", FILE_LIST_DIRECTORY,
FILE_SHARE_READ | FILE_SHARE_WRITE | FILE_SHARE_DELETE,
NULL, OPEN_EXISTING,
FILE_FLAG_BACKUP_SEMANTICS, NULL);
if (hDir != INVALID_HANDLE_VALUE) {
printf("start watch\n");
if (ReadDirectoryChangesW(hDir, &fni, sizeof(fni), FALSE,
FILE_NOTIFY_CHANGE_FILE_NAME | FILE_NOTIFY_CHANGE_LAST_WRITE,
&dwRC, NULL, NULL))
{
pfni = (PFILE_NOTIFY_INFORMATION)&fni;
printf("%p [%ls]\n", (void*)pfni->NextEntryOffset, pfni->FileName);
//printf("%p [%*ls]\n", (void*)pfni->NextEntryOffset, pfni->FileNameLength, pfni->FileName);
}
CloseHandle(hDir);
}
return 0;
}


[John Z]

To add a bit more this is still using WIN 11 23H2 not the troublesome WIN 11 24H2. Version 12 on both OSs opened the project and the IDE starts as it was when closed.

Also all source files are in the Source file window and are accessed without any issue.

John Z

[Pelle]

Shutting down the IDE is a complicated process: lots of events triggered, and messages sent or posted.

There is a "checkpoint" in the code after which the order of events can differ, possibly changing the result somewhat. If I move the saving of workspace windows before this point, the result seems more predictable (here on Windows 10).