search

topherCantrell / computerarcheology

All of the code and resources backing computerarcheology.com (moving from SVN there)
http://computerarcheology.com
41 stars 10 forks source link

ArcadePhoenix.20240817 #25

Closed Sorbas2020 closed 2 months ago

Sorbas2020 commented 2 months ago

Better overview for the RAM usage. Preparation for upcomming analyis. Separation of ghost codes from older versions of the game development. Further excavation work.

topherCantrell commented 2 months ago

This all looks fantastic. I tweaked the web generator to allow for your "---" separators in the RAM USE. That's a great idea.

Sorbas2020 commented 2 months ago

Thank you. And have a nice Weekend.

Christopher Cantrell @.***> schrieb am Sa., 17. Aug. 2024, 14:46:

This all looks fantastic. I tweaked the web generator to allow for your "---" separators in the RAM USE. That's a great idea.

— Reply to this email directly, view it on GitHub https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294850134, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOD3N4NBZPRFHCKKTPALWVTZR5A2DAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHA2TAMJTGQ . You are receiving this because you authored the thread.Message ID: @.***>

Sorbas2020 commented 2 months ago

Hi Christopher i am afraid i did not fully understand the syntax of the pseudo codes for the web generator. Do you have a documentation for it? e.g. does {} only work for the call statement?

Greetings Peter

Christopher Cantrell @.***> schrieb am Sa., 17. Aug. 2024, 14:46:

This all looks fantastic. I tweaked the web generator to allow for your "---" separators in the RAM USE. That's a great idea.

— Reply to this email directly, view it on GitHub https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294850134, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOD3N4NBZPRFHCKKTPALWVTZR5A2DAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHA2TAMJTGQ . You are receiving this because you authored the thread.Message ID: @.***>

topherCantrell commented 2 months ago

I added some documentation here: https://github.com/topherCantrell/computerarcheology/blob/master/README.md#the-names_in_code-tool

Let me know if that helps, and I can tell you more.

For the most part, the "names_in_code" tool that runs as part of the web deployment will update all these whether you want it to or not. But there is some syntax for overriding it.

On Sat, Aug 17, 2024 at 5:10 PM Sorbas2020 @.***> wrote:

Hi Christopher i am afraid i did not fully understand the syntax of the pseudo codes for the web generator. Do you have a documentation for it? e.g. does {} only work for the call statement?

Greetings Peter

Christopher Cantrell @.***> schrieb am Sa., 17. Aug. 2024, 14:46:

This all looks fantastic. I tweaked the web generator to allow for your "---" separators in the RAM USE. That's a great idea.

— Reply to this email directly, view it on GitHub < https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294850134>,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AOD3N4NBZPRFHCKKTPALWVTZR5A2DAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHA2TAMJTGQ>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294999516, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKK6QPY5H4UWFDHY2ZJTNLZR7C4XAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHE4TSNJRGY . You are receiving this because you modified the open/close state.Message ID: @.***>

Sorbas2020 commented 2 months ago

Yes, that helps. Now i know how to use it. Thank you.

Christopher Cantrell @.***> schrieb am So., 18. Aug. 2024, 20:43:

I added some documentation here:

https://github.com/topherCantrell/computerarcheology/blob/master/README.md#the-names_in_code-tool

Let me know if that helps, and I can tell you more.

For the most part, the "names_in_code" tool that runs as part of the web deployment will update all these whether you want it to or not. But there is some syntax for overriding it.

On Sat, Aug 17, 2024 at 5:10 PM Sorbas2020 @.***> wrote:

Hi Christopher i am afraid i did not fully understand the syntax of the pseudo codes for the web generator. Do you have a documentation for it? e.g. does {} only work for the call statement?

Greetings Peter

Christopher Cantrell @.***> schrieb am Sa., 17. Aug. 2024, 14:46:

This all looks fantastic. I tweaked the web generator to allow for your "---" separators in the RAM USE. That's a great idea.

— Reply to this email directly, view it on GitHub <

https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294850134>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AOD3N4NBZPRFHCKKTPALWVTZR5A2DAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHA2TAMJTGQ>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub < https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294999516>,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABKK6QPY5H4UWFDHY2ZJTNLZR7C4XAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHE4TSNJRGY>

. You are receiving this because you modified the open/close state.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2295353644, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOD3N4PSFBRXNHVSXJD77ITZSDTNZAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGM2TGNRUGQ . You are receiving this because you authored the thread.Message ID: @.***>

Sorbas2020 commented 2 months ago

Hi Christopher,

Some of my added pseudo codes are removed. I dont know why. Did i something wrong? e.g. for line: 0149: 21 A3 43 LD HL,$43A3 ; {ram.GameAndDemoOrSplash}

the address was at the ram file: | 43A3 | GameAndDemoOrSplash | Game and demo:0 Intro splash:2 |

the same happened with line 0377

Please check.

Greetings Peter

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Virenfrei.www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Am So., 18. Aug. 2024 um 20:43 Uhr schrieb Christopher Cantrell < @.***>:

I added some documentation here:

https://github.com/topherCantrell/computerarcheology/blob/master/README.md#the-names_in_code-tool

Let me know if that helps, and I can tell you more.

For the most part, the "names_in_code" tool that runs as part of the web deployment will update all these whether you want it to or not. But there is some syntax for overriding it.

On Sat, Aug 17, 2024 at 5:10 PM Sorbas2020 @.***> wrote:

Hi Christopher i am afraid i did not fully understand the syntax of the pseudo codes for the web generator. Do you have a documentation for it? e.g. does {} only work for the call statement?

Greetings Peter

Christopher Cantrell @.***> schrieb am Sa., 17. Aug. 2024, 14:46:

This all looks fantastic. I tweaked the web generator to allow for your "---" separators in the RAM USE. That's a great idea.

— Reply to this email directly, view it on GitHub <

https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294850134>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AOD3N4NBZPRFHCKKTPALWVTZR5A2DAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHA2TAMJTGQ>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub < https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294999516>,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABKK6QPY5H4UWFDHY2ZJTNLZR7C4XAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHE4TSNJRGY>

. You are receiving this because you modified the open/close state.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2295353644, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOD3N4PSFBRXNHVSXJD77ITZSDTNZAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGM2TGNRUGQ . You are receiving this because you authored the thread.Message ID: @.***>

topherCantrell commented 2 months ago

By default, the tool will automatically add/remove/change the "{...}" comments. It doesn't know that "LD HL,$43A3" is a memory address. Trying telling it explicitly like this:

0149: 21 A3 43 LD HL,$43A3 ; {+}

or

0149: 21 A3 43 LD HL,$43A3 ; {+ram.GameAndDemoOrSplash}

The plus SHOULD make it respect it (and update it if needed)

Let me know!

On Mon, Aug 19, 2024 at 11:45 AM Sorbas2020 @.***> wrote:

Hi Christopher,

Some of my added pseudo codes are removed. I dont know why. Did i something wrong? e.g. for line: 0149: 21 A3 43 LD HL,$43A3 ; {ram.GameAndDemoOrSplash}

the address was at the ram file: | 43A3 | GameAndDemoOrSplash | Game and demo:0 Intro splash:2 |

the same happened with line 0377

Please check.

Greetings Peter

< https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>

Virenfrei.www.avast.com < https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Am So., 18. Aug. 2024 um 20:43 Uhr schrieb Christopher Cantrell < @.***>:

I added some documentation here:

https://github.com/topherCantrell/computerarcheology/blob/master/README.md#the-names_in_code-tool

Let me know if that helps, and I can tell you more.

For the most part, the "names_in_code" tool that runs as part of the web deployment will update all these whether you want it to or not. But there is some syntax for overriding it.

On Sat, Aug 17, 2024 at 5:10 PM Sorbas2020 @.***> wrote:

Hi Christopher i am afraid i did not fully understand the syntax of the pseudo codes for the web generator. Do you have a documentation for it? e.g. does {} only work for the call statement?

Greetings Peter

Christopher Cantrell @.***> schrieb am Sa., 17. Aug. 2024, 14:46:

This all looks fantastic. I tweaked the web generator to allow for your "---" separators in the RAM USE. That's a great idea.

— Reply to this email directly, view it on GitHub <

https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294850134>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AOD3N4NBZPRFHCKKTPALWVTZR5A2DAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHA2TAMJTGQ>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub <

https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294999516>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ABKK6QPY5H4UWFDHY2ZJTNLZR7C4XAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHE4TSNJRGY>

. You are receiving this because you modified the open/close state.Message ID: @.***>

— Reply to this email directly, view it on GitHub < https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2295353644>,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AOD3N4PSFBRXNHVSXJD77ITZSDTNZAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGM2TGNRUGQ>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2297000247, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKK6QPCO7SK4PB4BUR7UW3ZSIOJXAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJXGAYDAMRUG4 . You are receiving this because you modified the open/close state.Message ID: @.***>

topherCantrell commented 2 months ago

You are the first person, besides me, to use these tools. I really need to clean them up and document them! Feel free to jump in the madness with me!

On Mon, Aug 19, 2024 at 11:52 AM Christopher Cantrell < @.***> wrote:

By default, the tool will automatically add/remove/change the "{...}" comments. It doesn't know that "LD HL,$43A3" is a memory address. Trying telling it explicitly like this:

0149: 21 A3 43 LD HL,$43A3 ; {+}

or

0149: 21 A3 43 LD HL,$43A3 ; {+ram.GameAndDemoOrSplash}

The plus SHOULD make it respect it (and update it if needed)

Let me know!

On Mon, Aug 19, 2024 at 11:45 AM Sorbas2020 @.***> wrote:

Hi Christopher,

Some of my added pseudo codes are removed. I dont know why. Did i something wrong? e.g. for line: 0149: 21 A3 43 LD HL,$43A3 ; {ram.GameAndDemoOrSplash}

the address was at the ram file: | 43A3 | GameAndDemoOrSplash | Game and demo:0 Intro splash:2 |

the same happened with line 0377

Please check.

Greetings Peter

< https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>

Virenfrei.www.avast.com < https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Am So., 18. Aug. 2024 um 20:43 Uhr schrieb Christopher Cantrell < @.***>:

I added some documentation here:

https://github.com/topherCantrell/computerarcheology/blob/master/README.md#the-names_in_code-tool

Let me know if that helps, and I can tell you more.

For the most part, the "names_in_code" tool that runs as part of the web deployment will update all these whether you want it to or not. But there is some syntax for overriding it.

On Sat, Aug 17, 2024 at 5:10 PM Sorbas2020 @.***> wrote:

Hi Christopher i am afraid i did not fully understand the syntax of the pseudo codes for the web generator. Do you have a documentation for it? e.g. does {} only work for the call statement?

Greetings Peter

Christopher Cantrell @.***> schrieb am Sa., 17. Aug. 2024, 14:46:

This all looks fantastic. I tweaked the web generator to allow for your "---" separators in the RAM USE. That's a great idea.

— Reply to this email directly, view it on GitHub <

https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294850134>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AOD3N4NBZPRFHCKKTPALWVTZR5A2DAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHA2TAMJTGQ>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub <

https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294999516>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ABKK6QPY5H4UWFDHY2ZJTNLZR7C4XAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHE4TSNJRGY>

. You are receiving this because you modified the open/close state.Message ID: @.***>

— Reply to this email directly, view it on GitHub < https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2295353644>,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AOD3N4PSFBRXNHVSXJD77ITZSDTNZAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGM2TGNRUGQ>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2297000247, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKK6QPCO7SK4PB4BUR7UW3ZSIOJXAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJXGAYDAMRUG4 . You are receiving this because you modified the open/close state.Message ID: @.***>

Sorbas2020 commented 2 months ago

Ok. I was just a little bit confused, but now it should work like that. https://github.com/topherCantrell/computerarcheology/pull/26

Thank you and have a nice evening.

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Virenfrei.www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Am Mo., 19. Aug. 2024 um 18:52 Uhr schrieb Christopher Cantrell < @.***>:

By default, the tool will automatically add/remove/change the "{...}" comments. It doesn't know that "LD HL,$43A3" is a memory address. Trying telling it explicitly like this:

0149: 21 A3 43 LD HL,$43A3 ; {+}

or

0149: 21 A3 43 LD HL,$43A3 ; {+ram.GameAndDemoOrSplash}

The plus SHOULD make it respect it (and update it if needed)

Let me know!

On Mon, Aug 19, 2024 at 11:45 AM Sorbas2020 @.***> wrote:

Hi Christopher,

Some of my added pseudo codes are removed. I dont know why. Did i something wrong? e.g. for line: 0149: 21 A3 43 LD HL,$43A3 ; {ram.GameAndDemoOrSplash}

the address was at the ram file: | 43A3 | GameAndDemoOrSplash | Game and demo:0 Intro splash:2 |

the same happened with line 0377

Please check.

Greetings Peter

<

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>

Virenfrei.www.avast.com <

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Am So., 18. Aug. 2024 um 20:43 Uhr schrieb Christopher Cantrell < @.***>:

I added some documentation here:

https://github.com/topherCantrell/computerarcheology/blob/master/README.md#the-names_in_code-tool

Let me know if that helps, and I can tell you more.

For the most part, the "names_in_code" tool that runs as part of the web deployment will update all these whether you want it to or not. But there is some syntax for overriding it.

On Sat, Aug 17, 2024 at 5:10 PM Sorbas2020 @.***> wrote:

Hi Christopher i am afraid i did not fully understand the syntax of the pseudo codes for the web generator. Do you have a documentation for it? e.g. does {} only work for the call statement?

Greetings Peter

Christopher Cantrell @.***> schrieb am Sa., 17. Aug. 2024, 14:46:

This all looks fantastic. I tweaked the web generator to allow for your "---" separators in the RAM USE. That's a great idea.

— Reply to this email directly, view it on GitHub <

https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294850134>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AOD3N4NBZPRFHCKKTPALWVTZR5A2DAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHA2TAMJTGQ>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub <

https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2294999516>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ABKK6QPY5H4UWFDHY2ZJTNLZR7C4XAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHE4TSNJRGY>

. You are receiving this because you modified the open/close state.Message ID: @.***>

— Reply to this email directly, view it on GitHub <

https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2295353644>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AOD3N4PSFBRXNHVSXJD77ITZSDTNZAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGM2TGNRUGQ>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub < https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2297000247>,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABKK6QPCO7SK4PB4BUR7UW3ZSIOJXAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJXGAYDAMRUG4>

. You are receiving this because you modified the open/close state.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/topherCantrell/computerarcheology/pull/25#issuecomment-2297013627, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOD3N4IYOKQONHEG6BOCU7TZSIPFXAVCNFSM6AAAAABMVMB3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJXGAYTGNRSG4 . You are receiving this because you authored the thread.Message ID: @.***>