issues
search
GemTalk
/
PharoGemStoneFFI
GemStone GCI access via Pharo FFI
MIT License
1
stars
3
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Need smalltalk logic to call thread safe library GciTsNbLogout
#16
ericwinger
opened
8 months ago
0
Source line endings are not normalized in git
#15
martinmcclure
closed
1 year ago
1
[#13] Enable caching of callout methods
#14
akgrant43
opened
1 year ago
3
Enable caching of callout methods
#13
martinmcclure
opened
1 year ago
0
Should GsSession>>logout signal an error if not logged in?
#12
martinmcclure
opened
3 years ago
0
GsSessionTest>>testLogin -- GciThreadSafeInterface did not understand #ifTrue:
#11
martinmcclure
closed
3 years ago
2
GsExternalByteString>>asByteString leaks memory
#10
martinmcclure
closed
3 years ago
2
executeStringAndFetchResultString: can answer extra characters
#9
martinmcclure
closed
3 years ago
2
FFICalloutAPI>>function:library: Ensure moduleNameOrLibrary
#8
akgrant43
closed
3 years ago
1
temp obj space gets filled up on logout
#7
ericwinger
closed
3 years ago
2
gci error handling (part 1 - click on Explorer in launcher)
#6
dalehenrich
opened
3 years ago
2
SparkleFFI should trim white space on strings passed to C that are used in the NRS
#5
dalehenrich
opened
3 years ago
0
A GCIError handler would be useful to have in the event of an unexpected GCIError when running Sparkle via GCI
#4
dalehenrich
closed
3 years ago
4
SparkleFFI package names should have a `SparkleFFI-` prefix ...
#3
dalehenrich
closed
1 year ago
3
Improvement in error handling if image forcibly killed and session is gone
#2
ericwinger
closed
3 years ago
1
Result strings contain null byte
#1
kurtkilpela
closed
3 years ago
6