Author Topic: weird Compiler message  (Read 2450 times)

0 Members and 1 Guest are viewing this topic.

Peter

  • Full Member
  • ***
  • Posts: 161
weird Compiler message
« on: November 04, 2010, 09:11:34 AM »
Deleted
« Last Edit: May 05, 2015, 12:47:47 PM by Peter »

Charles Pegge

  • Admin Support Member
  • *****
  • Posts: 4097
    • Oxygen Basic
Re: weird Compiler message
« Reply #1 on: November 04, 2010, 10:08:09 AM »

Hi Peter,

It looks as though a Basic error has fallen through to the assembler. Can you isolate the block of code causing this?
Sometimes the error is not obvious or may be caused by the compiler so isolation is the only way to trap it.

Charles

Charles Pegge

  • Admin Support Member
  • *****
  • Posts: 4097
    • Oxygen Basic
Re: weird Compiler message
« Reply #2 on: November 04, 2010, 11:12:14 AM »

I think this last problem is due to the low level binding which requires an exact compatibility match for all parameters.

When library functions are bound this way (without prototype declaration) then O2 strings should be passed as *S instead of S, because they are double pointered.


Charles

o2admin

  • Administrator
  • *****
  • Posts: 21
  • OxygenBasic
    • Oxygen Basic
Re: weird Compiler message
« Reply #3 on: November 04, 2010, 02:41:53 PM »

Hi Peter,

A have found a few more things:

got as far as black window.
I have marked the problem areas with 'itr

Charles

[attachment deleted by admin]

Charles Pegge

  • Admin Support Member
  • *****
  • Posts: 4097
    • Oxygen Basic
Re: weird Compiler message
« Reply #4 on: November 04, 2010, 08:23:00 PM »

If you specifiy an itermax of say 64 then the fractal will appear in red.

Charles