Ficl - small systems scripting with OO Activity
Brought to you by:
jsadler
Activity for Ficl - small systems scripting with OO
-
john sadler posted a comment on discussion Help
After a long absence I am working actively on Ficl again. If you need help, I will do my best. I need to know the following information where relevant: What version of Ficl What compiler What target architecture Description of the problem with any error messages you may be getting What you have already tried Anything else that might provide context
-
I know this reply is too late, but for the record, Ficl is not wedded to any particular OS, and will work nicely with any target where sizeof(void *)is either 4 or 8, and there is a standard C or C++ compiler. Unix-derived operating systems are great targets. You can also use Ficl on targets without an OS or filesystem.
-
Ficl4 is retiring
-
Ficl4 is retiring
-
Ficl - small systems scripting with OO released /OldFiles/Ficl4 (retired)/ficl-4.1.0.zip
-
-
-
-
New compilers (GCC >4) may not work
-
Looking at this now after many years doing other things. I have a successful Ficl3 build under clang on MacOS and will check this also on gcc. So far so good - all tests passing. Was this issue specifically with Ficl4?
-
New compilers (GCC >4) may not work
-
ficlVmInnerLoop hard loop
-
typedef intptr_t ficlInstruction; in ficl.h
-
ficlDictionaryLock in ficlDictionaryLookup
-
Thanks for this. Confirmed this bug does not exist in Ficl3
-
"bit" is a reserved word in some compilers
-
Bug in cleanup code after exit
-
Confirmed working correctly in Ficl3
-
Win32.c is no good when building for win32 in cygwin...
-
FPICK does not work
-
tarball expands into .
-
tarball expands into .
-
ficlSystemDestroy bug.
-
keeping this open. Not clear whether there will be another ficl4 release
-
debugger crash
-
Not clear whether there will be another ficl4 release. Will keep this open while making that decision.
-
PICK works incorrectly
-
ficlVmGetContext
-
This appears to be a Ficl4 issue. Not clear whether there will be another Ficl 4 release, but will keep this open
-
typo in system.c (4.0.31)
-
Not sure when or whether there will be another Ficl4 release.
-
complete CORE EXT words
-
softwords
-
Belated thanks for this. Ficl3 implements (1) already and I will be sure to carry it forward. I have included (2) as well for release in Ficl304 and will carry it forward. Apologies for the glacial pace. I am resuming work on Ficl after a long hiatus
-
ficlVmGetContext
-
incorrect declaration in unix.c
-
Fixed
-
...and we're back - almost
-
Anton Ertl posted a comment on ticket #20
I have not looked at FICL, so I don't know how it uses setjmp/longjump. In Gforth we use setjump/longjump to get back from the signal handler (for stuff like invalid memory access, Ctrl-C, stack underflow, division by zero) to the engine. All these conditions produce a Forth-level exception, which helps getting around the problem for gforth-fast (the benchmarking engine): All stack pointers and the instruction pointer are reset to the value stored in the exception frame, so if we lose the values...
-
Christian Huttg created ticket #20
New compilers (GCC >4) may not work
-
-
-
-
-
-
-
-
1