XYplorer Beta Club

We can have a default.inc, which is always loaded in RAM. Scripts doesn't need to explicitly include this file. The "include" line is only needed for user-created *.inc other than default.inc.

PeterH wrote:In the conversations we had over time, I came to the conclusion that every script should have a Caption / Label, so that I think you are on the safe side with:

Code: Select all

include "_functions.inc"

"Main"
    $a = <<<>>>
hello world
>>>;

    text $a;

(Don't forget to indent the $a= in this case...)

Actually if the include file has only functions, then including it at the END requires no messing with indentation:

Thanks highend, PeterH, Sammay,
indentation was indeed the culprit. It didn't occur to me, because the script worked fine will all those indents, until I added the include-line to it.

Those whitespace rules keep driving me out of my mind. After adding my own heredoc sections - strictly by copy & paste & overwrite - it stopped working. Took me a long time and zillions of WinMerge compares to track this one down: one single invisible blank at the end of my heredoc-closing. Must have happened during copy & paste, part of the editor's setting to do "smart pasting" to keep inserted words apart.

I had known all along that whitespace up front is a tricky business, but whitespace at the very end never was a problem - until this incident.

Well, these are the rules of HEREDOC. It's the same in PHP and it makes sense IMO. Tip: Let your editor mark white spaces and the guessing is over.

Please allow using variables to refer to namespaces (somehow)

I'm still not convinced of using namespaces. Why not give them a unique name?

Can you explain?

(The situation I understand is to be able to differentiate between XY-native and User. Though I think I'd even use that rarely, if at all.)

when I want to call a function in the same namespace from another function.

And if this:   $ns = self('namespace');   were possible, I wouldn't have to write self(namespace) a lot.

The namespace feature will stay "unofficial/in freeze" for the time being.

1. Where should I place the include statement? I tried thisand "2nd" shows up greyed out. Howeverworks fine.

2. Something like thisis not parsed correctly. The debug shows a ") {".

You should place such an include - i.e. an include that includes complete functions, where you would place the functions themselves.

If you place an include at the very beginning: make sure the main part starts with a label. (You should do this anyway!)
You may easy place the include at the very end.
And you may place include somewhere in the middle - in front of a line with a label.

I hope I got it all

(An include may just refer to some plane lines, without any label. These must be located where these lines are needed )

1) the line immediately following a function has to unindented, as if the function were a subscript. Therefore, this will work:Because of this rule, and because functions can be accessed from the whole script regardless of where and when they are defined, I suggest you either:
a) define all functions before the main script, and start the main script with an unindented line or caption, or
b) define all functions after all of the main script content. In this case the main script's first line can be indented, because everything till the next unindented line is processed as the script. orOTOH, INCLUDE itself must be written without indentation, but whether it's surrounding code be un-/indented depends on the included content.

2) http://www.xyplorer.com/xyfc/viewtopic. ... 50#p122820 default values for FUNCTION parameters only resolve XY or systemnative variables (<var>, %var%), but no function calls or other variables.

I see you found workaround for point 1), but I thought it would be better it just worked as expected. Tricky! Needed a larger rewrite. Side-effect: Now include, function, and namespace statements can be indented.
- Makes scripts look better.
- Also included stuff will now inherit the indent of the include statement.

what if the INCLUDEd content has heredocs?

admin wrote:- Also included stuff will now inherit the indent of the include statement.

Does that mean I won't be seeing menu items when including a "menu"-script? To my understanding, for menu items to be visible, they have to start flush left?

admin wrote:I see you found workaround for point 1), but I thought it would be better it just worked as expected. Tricky! Needed a larger rewrite. Side-effect: Now include, function, and namespace statements can be indented.
- Makes scripts look better.
- Also included stuff will now inherit the indent of the include statement.

Hm. Do you think of situations where I include
- a file with a (maybe hidden) script, i.e. not ending on a }
- a file with just a few plain statements, i.e. neither (labeled) script nor function (for inside a script)

And I hope you don't want to say that script files look better when you can't optically realize where scripts start?

OK: just guessing what you might think - I may be wrong