Add `VDBStartupA` into `jv:vdb/application`
This class is just a placeholder, all logic is in its superclass,
`VDBStatup`. The reason for this is the way the initial package
path is computed (see `AbstractOpratingSystem >> defaultPackagePath`)
The code there assumes that startup class is from the same package
as the application itself.
This way, we have a startup class in the application package but still
have `VDBStartup` available when only `jv:vdb` is loaded (like when
developing and.or using VDB from Smalltalk/X IDE.
"
jv:vdb - Visual / VM Debugger
Copyright (C) 2015-now Jan Vrany
This software is licensed under 'Creative Commons Attribution-NonCommercial 4.0 International License'
You may find a full license text in LICENSE.txt or at http://creativecommons.org/licenses/by-nc/4.0/
"
"{ Package: 'jv:vdb' }"
"{ NameSpace: Smalltalk }"
GDBVariableObjectExecutor subclass:#VDBVariableObjectExecutor
instanceVariableNames:''
classVariableNames:''
poolDictionaries:''
category:'VDB-Core'
!
!VDBVariableObjectExecutor class methodsFor:'documentation'!
copyright
"
jv:vdb - Visual / VM Debugger
Copyright (C) 2015-now Jan Vrany
This software is licensed under 'Creative Commons Attribution-NonCommercial 4.0 International License'
You may find a full license text in LICENSE.txt or at http://creativecommons.org/licenses/by-nc/4.0/
"
! !
!VDBVariableObjectExecutor methodsFor:'finalization'!
finalize
debugger isConnected ifTrue:[
debugger send: (VDBMI_vdb_var_delete arguments: (Array with: '-c' with: name))
].
"Created: / 06-07-2019 / 00:37:10 / Jan Vrany <jan.vrany@fit.cvut.cz>"
! !
!VDBVariableObjectExecutor class methodsFor:'documentation'!
version_HG
^ '$Changeset: <not expanded> $'
! !