Correctly handle GET-CURRENT-EXEC being null
Correctly handle GET-CURRENT-EXEC being null

GET-CURRENT-EXEC defaults to returning NULL, not BLANK!.

Incorrectly thinking it returned blank meant that platforms with no
special API handling for getting the current executable (e.g. Haiku)
would not run.

hostilefork/rebol,giuliolunati/ren-c,giuliolunati/ren-c,giuliolunati/ren-c,giuliolunati/ren-c,hostilefork/rebol,giuliolunati/ren-c,hostilefork/rebol,hostilefork/rebol,hostilefork/rebol,hostilefork/rebol