My simple Win32 Compiler

[FlierMate]

......Even if that lot is beyond you for the moment, just remember that it is a mistake to try to apply high-level text processing commands to the input.

MarkMLl

Noted with thanks, it is beyond my level at the moment, but I appreciate you for pointing out the mistake in the program.

[MarkMLl]

That was intended to be more of a general warning that anything else, but /is/ derived from having done this sort of thing multiple times without the questionable benefit of a computer science background.

MarkMLl

[lucamar]

[...] I have disowned and removed the source code from everywhere.

Badly done, IMHO. You should own it even as a "failure" and keep it around somewhere, even if just as an example of how things should NOT be done.

Even (or specially) bad code can be a very useful didactic resource: most students will look at it and maybe laugh a little at its clumsiness in public ... but privately they will think "Wow! I was about to do exactly that! Thank the gods I saw it in time!", and it'll at least have served a purpose as an aid in learning.

[hansotten]

IF (note the big IF) you can find it at a reasonable price, the book : Per Brinch Hansen on Pascal Compilers might very well be the best introductory text on compilers ever written but it's out of print and used copies are usually sold for exorbitant prices (don't pay more than $50.00 and a reasonable shipping fee)

I is here: http://pascal.hansotten.com/per-brinch-hansen/

[FlierMate]

Badly done, IMHO. You should own it even as a "failure" and keep it around somewhere, even if just as an example of how things should NOT be done.

Even (or specially) bad code can be a very useful didactic resource: most students will look at it and maybe laugh a little at its clumsiness in public ... but privately they will think "Wow! I was about to do exactly that! Thank the gods I saw it in time!", and it'll at least have served a purpose as an aid in learning.

Never thought of that, thanks. I learn the right attitude from you- own it as a failure. Nevertheless, I think I will be able to rewrite the code with minor improvement if I want to.
For example, I will use Cardinal for DWORD, and Array [1..2] of Cardinal for 4-byte address and 4-byte size. However, I am not sure how the Cardinal will be stored in binary - MSB and LSB in reversed order?

I is here: http://pascal.hansotten.com/per-brinch-hansen/

OMG  , you're an expert. I am speechless, the book(s) are free!

[MarkMLl]

For example, I will use Cardinal for DWORD, and Array [1..2] of Cardinal for 4-byte address and 4-byte size. However, I am not sure how the Cardinal will be stored in binary - MSB and LSB in reversed order?

Stick to native numeric representation until you really need something different, i.e. only do the conversion at input/output time.

MarkMLl

[FlierMate]

Stick to native numeric representation until you really need something different, i.e. only do the conversion at input/output time.

MarkMLl

  I am grateful for your guidance( tips & tricks) thus far.

[440bx]

I is here: http://pascal.hansotten.com/per-brinch-hansen/

You've really done a a great job with your website.

I am extremely pleased to see the book Brinch Hansen on Pascal Compilers available for download.  IMO, it's the best starting point.  Anyone interested in compilers should read that book at least twice.

I am grateful for your guidance( tips & tricks) thus far.

Read the Brinch Hansen on Pascal Compilers book, you'll be glad you did (for multiple reasons.)

[MarkMLl]

I is here: http://pascal.hansotten.com/per-brinch-hansen/

That's a particularly good collection. I've just checked and I note that the web page is archived at archive.org, but the PDFs might not be... I don't know whether that's fixable. Alternatively I hope you've got it archived/mirrored somewhere as your professional legacy.

MarkMLl

[valdir.marcos]

IF (note the big IF) you can find it at a reasonable price, the book : Per Brinch Hansen on Pascal Compilers might very well be the best introductory text on compilers ever written but it's out of print and used copies are usually sold for exorbitant prices (don't pay more than $50.00 and a reasonable shipping fee)

I is here: http://pascal.hansotten.com/per-brinch-hansen/

I is here: http://pascal.hansotten.com/per-brinch-hansen/

OMG  , you're an expert. I am speechless, the book(s) are free!

I is here: http://pascal.hansotten.com/per-brinch-hansen/

You've really done a a great job with your website.
I am extremely pleased to see the book Brinch Hansen on Pascal Compilers available for download.  IMO, it's the best starting point.  Anyone interested in compilers should read that book at least twice.

Now prices will fall...

[valdir.marcos]

I is here: http://pascal.hansotten.com/per-brinch-hansen/

You've really done a a great job with your website.

+1

I am extremely pleased to see the book Brinch Hansen on Pascal Compilers available for download.  IMO, it's the best starting point.  Anyone interested in compilers should read that book at least twice.

+1

[FlierMate]

CLARIFICATION:


I wish to point out that this Satay Compiler might generates EXE which will be falsely detected by antivirus software as Trojan.

If you are concerned, my original post about this issue is on FASM official message board: https://board.flatassembler.net/topic.php?t=21786 (External Link)

Please refer to attached screenshots showing Text1.txt.EXE was first reported as malware by Windows Defender. After I submitted report, Microsoft Security Intelligence removed the detection (for that particular EXE only).

The EXE generated by Satay Compiler makes calls to the following Win32 API functions only:
1. GetStdHandle
2. ReadConsoleA
3. WriteConsoleA
4. ExitProcess

It does nothing malicious. It is unclear to me as to why some AV software reporting these canned EXEs as trojan.

[marcov]

The EXE generated by Satay Compiler makes calls to the following Win32 API functions only:
1. GetStdHandle
2. ReadConsoleA
3. WriteConsoleA
4. ExitProcess

It does nothing malicious. It is unclear to me as to why some AV software reporting these canned EXEs as trojan.

It is very simple. Antivirus authors are lazy and reverse the burden of proof, basically denying everything unless proven otherwise.

So assume they simply block everything, and then only start adding exceptions for well known "EXE" signatures. If you think that through, you actually get pretty close to actual antivirus behaviour. It can't be coincidence :-)

So inventing a new kind of EXE signature only invites trouble.

[FlierMate]

The EXE generated by Satay Compiler makes calls to the following Win32 API functions only:
1. GetStdHandle
2. ReadConsoleA
3. WriteConsoleA
4. ExitProcess

It does nothing malicious. It is unclear to me as to why some AV software reporting these canned EXEs as trojan.

It is very simple. Antivirus authors are lazy and reverse the burden of proof, basically denying everything unless proven otherwise.

So assume they simply block everything, and then only start adding exceptions for well known "EXE" signatures. If you think that through, you actually get pretty close to actual antivirus behaviour. It can't be coincidence :-)

So inventing a new kind of EXE signature only invites trouble.

You are most probably right, because you are developer of Free Pascal Compiler.

    Thank you for the insights.

[FlierMate]

Nonetheless, I have hosted this closed-source simple compiler publicly on :

https://sataycompiler.tech/

(Only the IDE itself has Pascal source code)