Author Topic: Can't identify next operand  (Read 145 times)

0 Members and 1 Guest are viewing this topic.

Brian Alvarez

  • Hero Member
  • *****
  • Posts: 699
    • PluriBASIC
Can't identify next operand
« on: January 30, 2021, 12:38:13 pm »
 Hello Charles, i implemented the double pointer to fix an issue as you suggested like this:

Code: [Select]
FUNCTION OPTIONALLYADDFUNC(?ARR_STRINGDATA *sd, LONG *index, STRING **ce) AS LONG

END FUNCTION

 This fixes all the issues with any variable type, but if i ever invoke the function using a literal string like this:

Code: [Select]
OPTIONALLYADDFUNC(sd, index, "0, ")
 I get this during compilation:

Code: [Select]
ERROR: ASSEMBLER:
 ERR: lea eax,"0, "!!  Can't identify next operand '
LINE: 1094
FILE: "main source

 I know removing the double pointer fixes it but i cant generate different code depending on how it is invoked because a function can be invoked in several ways throgouth the program. Is there another way to avoid this?

 The code compiles fine when it is a function, like this:

Code: [Select]
OPTIONALLYADDFUNC(sd, index, TRIM$("0, ", 0, null))
 So i wonder if this is an issue with Oxygen?










Charles Pegge

  • Admin Support Member
  • *****
  • Posts: 4486
    • Oxygen Basic
Re: Can't identify next operand
« Reply #1 on: February 02, 2021, 01:30:09 am »
Hi Brian,

Theproblem is passing string literals and string expressions to functions expecting an array block of strings (double pointered).

Currently, this is resolved by passing literals and expressions to a temp string beforehand and passing the temp string, but I'm working on a solution.

John

  • Hero Member
  • *****
  • Posts: 3966
Re: Can't identify next operand
« Reply #2 on: February 02, 2021, 01:58:35 am »
The literal vs. variable state isn't an easy nut to crack when using them as arguments to procedures. SB converts all string literals to a temp null terminated string before passing them along. Literals are like comments that assume to be code. Pointerless references.
« Last Edit: February 02, 2021, 05:00:12 pm by John »

Brian Alvarez

  • Hero Member
  • *****
  • Posts: 699
    • PluriBASIC
Re: Can't identify next operand
« Reply #3 on: February 03, 2021, 08:19:41 am »
 Thanks Charles!, i appreciate it. :)