I2CWRITE not writing anything on PIC18F45K80

[CuriousOne]

Yes I have read that.
But same manual also says that array size is limited for 16F series and only limited by available RAM on 18F, so I thought that this should work fine, but as it seems, it does not

Now I have another everlasting issue to solve - how to send $FE data via LCDOUT statement (it interprets $FE as command, not data transfer).
Solving this issue will help me to add ability to draw graphics to my ST7920 "Library".

[richard]

But same manual also says that array size is limited for 16F series and only limited by available RAM on 18F, so I thought that this should work fine

how can you interpret that to mean that writes involving array boundary violations are an acceptable programming technique ?

[CuriousOne]

Well, as my experience with ZX Spectrum BASIC shows (In case of array misreading: Error 3: Subscript wrong), when you do something not allowed, you will get an error message.
Even Visual Basic does that check.

[richard]

its totally up to you to decide how much time you are prepared to waste learning this lesson.

continually wheeling out the old "ZX Spectrum BASIC" excuse leads nowhere and never will , compiled code is what it is
you need to deal with it

[Ioannis]

Since the index to array can be number or calculation then it is not possible for the compiler to check that!

The interpreter is totally different story. Do not compare the two.

Richard has it just right.

Ioannis

[HenrikOlsson]

Exactly, we've been thru this before. Your beloved ZX Spectrum runs a BASIC interpreter which interprets and executes the code as it runs. It (the interpreter) can check things like out of bounds errors at run-time, a task that I'm sure makes array-indexing slow as f-k.

PBP is a compiler. It COMPILES your BASIC source into instructions that the PIC executes natively, it's not an interpreter. It is IMPOSSIBLE for the compiler to detect out of bounds issues at COMPILE TIME.

And even if the compiler was built to generate code that DID check array boundries on every access at runtime what do you suggest should happen when such an error is detected? It's not like there's a TV or monitor connected that can display the error message. Nope, the program would just crash with no way to tell the user why. In what way is that better than what it does now?

[CuriousOne]

Yes I know what is the difference between the compiler and interpreter.

And I'm not asking about RUNTIME error handling. I'm asking about boundary checking during the compile.
It can be clearly seen from the code that reading past array boundaries WILL occur in compiled code:

1. Compiler knows that X is starting from 0
2. Compiler knows that array is being read at X-16 position, which is definitely an error.

So some kind of notification like - "possible out of boundary array access" is very well possible and would be great.