[Gambas-user] Gambas scripter

[Ron]

Ron wrote:
> Ron wrote:
>>
>> Some first experiences building scripts using gbs2
>>
>> Is it possible to display the errors at end of the output?
>> If you execute a large script from shell and have a compile error you 
>> keep on scrolling up to see the error.
>>
>> Or even better when there is an error on a line, display the script 
>> source until that line number with the error below it.
>> Maybe this is difficult because of the way scripting works. And/or 
>> display line numbers in front of source code lines.
>>
>> Another thing, there is no way to get the file name of the script 
>> from within the code.
>>
>> Application.Args[0] = 
>> /tmp/gambas.1000/script-cache/75ee02d930493c0fdc45e92c5b297df5
>>
>> Application.Name =  6dc71006365626c9524efb11972ce2af
>>
>> Script name in this case was 'callerid.script'
>>
>
> Application.Path is also pointing to the cache/tmp directory instead 
> of the real location of the script.
> Application.Path = /tmp/gambas.1000/script-cache
>
> I begin to see now, why I couldn't use it that easily last time.
>
> If you have to start using things like 'EXEC [ "pwd" ] TO sPwd' to get 
> the current dir it doesn't make sense to use a Gambas script.
>
>

If you have this script:
----------------
#! /usr/bin/env gbs2

PUBLIC SUB Main()

END

' a comment
----------------

You get:
----------------
/tmp/gambas.1000/12566/project.tmp/MMain.module:13: 'Main' already declared

' Gambas module file


PUBLIC SUB Main()

END

PUBLIC SUB Main()

' a comment

END
----------------

This is ok:

#! /usr/bin/env gbs2


PUBLIC SUB Main()

' comment

END
----------------
ie comments at the end of a script/outside SUBs are making the compiler 
crazy, and me too until I found out what the problem was. ;-p

Gambas 2.18.0

Regards,
Ron_2nd.