v4.10 small things

[janni]

Some leftovers from Basic got into mP v4.10:

- new functions in Conversions lib have names like LongWordToHex,
- Parameter Assistant also uses 'longword' instead of 'dword' in parameter lists.

Description of Glcd_PartialImage procedure claims that

Bitmap array can be located in both code and RAM memory (due to the mikroPascal PRO for PIC pointer to const and pointer to RAM equivalency).

What kind of equivalency is that, if the pointers differ in size? (Naturally, Glcd_PartialImage does not work with RAM arrays.)
The same claims appear in T6963c libs.

An obvious mistake in size of output string in IntToHex description in Help:

procedure IntToHex(input : integer; var output : array[64] of char);

[slavisa.zlatanovic]

Hi!

- new functions in Conversions lib have names like LongWordToHex...

We used the same names in all 3 compilers (C, Pascal & Basic). It was a developers decision.

- Parameter Assistant also uses 'longword' instead of 'dword' in parameter lists.

I have managed to reproduce it and I will inform our software developers about it.
Thanks for reporting!

Bitmap array can be located in both code and RAM memory (due to the mikroPascal PRO for PIC pointer to const and pointer to RAM equivalency).

Yes, this is a bug in the Help file. I will report it.
!!! Note that this statement is true for the Enhanced PIC16 family:

From Help file:

PIC16 Enhanced Family Specifics
PIC16 Enhanced family has 16-bit FSRs, FSRxL and FSRxH, capable of accessing entire RAM and Flash memory.
This makes pointers to constants and pointers to variables compatible.

procedure IntToHex(input : integer; var output : array[64] of char);

Yes, this is a bug in the Help file. I will report it.

[janni]

Hi Slavisa,

- new functions in Conversions lib have names like LongWordToHex...

We used the same names in all 3 compilers (C, Pascal & Basic). It was a developers decision.

Understandable, though it dos not make the routines any more Pascal-like . Maybe it would not take much work and maintenance effort to have two identical routines with different names (like LongWordToHex and dWordToHex)?

Bitmap array can be located in both code and RAM memory (due to the mikroPascal PRO for PIC pointer to const and pointer to RAM equivalency).

Yes, this is a bug in the Help file. I will report it.
!!! Note that this statement is true for the Enhanced PIC16 family...

Unfortunately, in the Enhanced PIC16 family the question of memory choice is moot, as there is not enough RAM to spare for keeping 1024 bytes of 128x64 bitmap.

[slavisa.zlatanovic]

Hi!

Understandable, though it dos not make the routines any more Pascal-like . Maybe it would not take much work and maintenance effort to have two identical routines with different names (like LongWordToHex and dWordToHex)?

I'll pass your suggestion to our developers.
Thanks for your suggestions.

Unfortunately, in the Enhanced PIC16 family the question of memory choice is moot, as there is not enough RAM to spare for keeping 1024 bytes of 128x64 bitmap.

I agree with you on this matter.