Procedure for writing our own code

[David Rabiner]

Enrico,

I noticed the "Seatbelts" sign fix in the other thread, and others have
suggested ways to code certain fixes.

I'm wondering how updates are going to be handled. I want to make sure, for

example, that I don't change pmsys737 or sysvar, and then have an update
come down the line that overwrites what we've individually done.

Are you going to send overwrites to pmsys737 or sysvar? Should we use the
scripts that I saw in an earlier thread?

Thanks. I'm having fun with this.

Warm regards,
David

[Enrico Schiratti]

Hi,

it is quite straight-forward...

You can use the released modules as they are, sysvar.txt is always the
reference and I will have to maintain it here... and pmsys737.txt is also
the reference which I have to update everyone with. The key is the fact that

a number of people is using it, so I can't know who changed what when.

You yourself have to decide when and how you break out from the reference
files and work on from there or whether you stick to the general ones.

The include mechanism could also be used inversely... i.e. you make your own

main file, include the reference 737 file and handle all extras that way...

i.e. inside of

pmsys_My_737.txt you add

include pmsys737.txt

Ciao

Enrico

"David Rabiner" wrote in message
news:281849.56025@wb.onvix.com...
> Enrico,
>
> I noticed the "Seatbelts" sign fix in the other thread, and others have
> suggested ways to code certain fixes.
>
> I'm wondering how updates are going to be handled. I want to make sure,
> for
>
> example, that I don't change pmsys737 or sysvar, and then have an update
> come down the line that overwrites what we've individually done.
>
> Are you going to send overwrites to pmsys737 or sysvar? Should we use
the
> scripts that I saw in an earlier thread?
>
> Thanks. I'm having fun with this.
>
> Warm regards,
> David
>