🚀 go-pugleaf

In article <8khf2d$7g4$1@nnrp1.deja.com>,
Robert AH Prins  <prino@bigfoot.com> wrote:
>Hi all,
>
>How do you put a literal in a string?
>
>Uh, what's wrong with "myline:= 'This is an example';"
>
>Nothing, but now assume that you're doing this many times in a program,
>and look at the code generated to make this assignment, you'll see that
>it comes to 18 bytes, excluding the string itself.
>
>How do you concatenate a string with a literal?
>
>Uh, what's wrong with "myline:= myline + 'This is an example';"
>
>Nothing, but now assume that you're doing this many times in a program,
>and look at the code generated to make this assignment, you'll see that
>it comes to 39 bytes, excluding the string itself.
>
>Wouldn't it be nice if you could shorten this? Faced with 20 of such
>assignments, and 18 concatenations in a program, I came up with this,
>but be warned that it _does not contain any error checking_, in other
>words, you have to know what you are doing!

Why not just write two procedures:

Procedure AssignString(var st:string; st2:string);
Procedure ConcatStr(var st;string; st2:string);

The implementations are trivial. That is just 13 bytes per call. Now if
you want to use open strings, it is 16 bytes per call. Those are for
near calls, fars use more.

No need to write any ASM code as the procedure code is included only
once no matter how many times it is used.

>var myline: string; {must be global}

Do you realize what nightmare these "must be global" things cause. Also
even if one adds to a global variable one still can use Pascal.

Osmo