The significant difference is that you MUST know the position of the string
you are relating to in the startup string.
Getting the whole string and parsing it yourself affords you the luxury of
adding to or deleting from the string with only having to deal with a
conditional statement to accommodate the change.
If the conditional statement would be encapsulated within a stored
procedure, there would likely only be one place that would require
maintenance other than the particular place the conditional statement was
directed.
RBase certainly gives you the ability to choose what suits you best though.
On Sunday, March 12, 2017 at 12:57:44 PM UTC-4, Michael Byerley wrote:
>
> This was started by Larry Lustig in the previous thread.
>
> This code segment could be placed anywhere relative to its purpose.
> Function declarations ONLY need to be done ONCE in an RBase session.
> Once declared, the DLCall rbase function can be used anywhere, anytime in
> an RBase session.
>
> {Begin Code}
>
>
> { Original Win32 Function Declaration: LPTSTR WINAPI GetCommandLine(void);}
>
> -- How to declare function in RBase:
>
>
> IF (CHKFUNC('GetCommandLine')) = 0 THEN
> STDCALL FUNCTION 'GetCommandLineA' alias 'GetCommandLine' () : TEXT
> ENDIF
>
>
> SET VAR vText TEXT = NULL
>
> SET VAR vText = (DLCALL('Kernel32', 'GetCommandLine'))
>
> PAUSE 2 USING .vText
>
> RETURN
>
> {End Code}
>
--
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
