Adding a Kanji ROM

Página 6/6
1 | 2 | 3 | 4 | 5 |

Por mars2000you

Enlighted (5990)

Imagen del mars2000you

22-11-2016, 03:32

You know, it's like the French grammar, there are general rules, exceptions in these rules and exceptions in the exceptions themselves!!!

But a Wiki must be coherent. If instructions are first added on a machine with a new version of MSX-BASIC, and that the corresponding hardware is defined in the standard of this machine, then these new instructions are standard.

Por gdx

Enlighted (4717)

Imagen del gdx

22-11-2016, 03:37

As say NYYRIKKI and Manuel, it's your way of classifying that is not enough.

Por mars2000you

Enlighted (5990)

Imagen del mars2000you

22-11-2016, 03:40

Do you dare to say to Kay Nishi that PCM is not standard on the Turbo R because the instructions begin with CALL ??? Hannibal

Por NYYRIKKI

Enlighted (5880)

Imagen del NYYRIKKI

22-11-2016, 09:30

I would say CALL PCMPLAY, CALL PCMREC and CALL PAUSE are standard extensions to MSX-BASIC in MSX tR, they are not Panasonic specific as also NIA-2001 has these commands (Although CALL PCMREC is broken... probably because of compiler error)

Por gdx

Enlighted (4717)

Imagen del gdx

22-11-2016, 11:19

I mean that it does not relevant to classify sometimes by version of Basic then by type of instruction. The version of Basic is already in compatibility sections. It's sufficient. We have to choose a classification type and always keep the same (and if necessary, change everything).

I think is more relevant to separate only the instructions by type (MSX-Basic or Extended Basic), and make sub-assemblies in "MSX-Basic set instructions page" (disk, graphic, music, sound, etc) and sub-assemblies in "Extended Basic instructions page" depending hardware which they are dedicated.

This is why I prefer to group the instructions of the PCM Turbo R.

Also sometimes you do too much. It starts with a good intention but it can complicate wiki readability and updates.

Another remark: In the pages where there is a lot missing We must first make the simplest or at least respect a logical order and useful.

Por mars2000you

Enlighted (5990)

Imagen del mars2000you

22-11-2016, 11:22

gdx wrote:

I think is more relevant to separate only the instructions by type (MSX-Basic or Extended Basic), and make sub-assemblies in "MSX-Basic set instructions page" (disk, graphic, music, sound, etc) and sub-assemblies in "Extended Basic instructions page" depending hardware which they are dedicated.

This is why I prefer to group the instructions of the PCM Turbo R.

Some people like to have all the standard MSX-BASIC instructions in the alphabetical order and some other people like to make sub-groups by hardware type. As the general overview that is automatically generated by the system gives the alphabetical order, you can indeed use the redactional part to present differently the overview of these instructions.

You can this way group the instructions of the PCM Turbo R on the page of the standard MSX-BASIC instructions. It will respect the coherence line that I've followed - new standard instructions for new hardware on a new version of MSX-BASIC (even if they have the syntax of extended instructions) - while giving another approach of the standard instructions than the alphabetical order.

Página 6/6
1 | 2 | 3 | 4 | 5 |