I don't think you should use foldable and flushable from the sounds of
things.
Foldable is used mostly to inline a computed value as a literal, and
flushable is used to indicate a word without side effects can be optimized
by the compiler to not be called if the output is not used.
Are you
You can easily get usage information, for example all (loaded) words that
call ``+``:
\ + usage.
There are some graphviz libraries that have been built to visualize various
parts of the compiler and either already can, or with some work, use the
tools.crossref vocabulary to look at word and
Have you looked at the io.serial vocabulary?
On Tue, May 24, 2016 at 7:33 AM, Alexander Ilin wrote:
> Hello!
>
> Did anyone work with COM-ports in Factor? Is there a vocab for that?
>
> ---=---
> Александр
>
>
>
Yes, a few different ways:
1) The entire file is parsed so if you have a word that is available in
0.98 but not in 0.97, you either have to call it dynamically:
"vm-version" "system" lookup-word execute( -- string )
or
2) Make separate files for 0.97 and 0.98, unfortunately we don't have
Dear all,
Is there a way to conditionally execute words?
For example: In one image "fuel" is loaded. In another image "fuel" is not
loaded.
Or: In Factor 0.98 there is a word "vm-version". In Factor 0.97 there is no
such word.
Is it possible to write a .factor-rc startup file that handles
Hello!
Are there any tools that can produce/visualize a graph of vocabulary
dependencies and/or call graphs (which words use which other words)?
It would be particularly interesting to see cases when two large vocab groups
depend on each other, where making a small common ground would
Thank you, John!
It seemed to me that there was no point to do the dip, but now I understand
that the quotation output will end up under the top stack element! Thanks again.
24.05.2016, 16:14, "John Benediktsson" :
> It creates a windows-file-info TUPLE under the stack and
Hello!
I have some CONSTANT: words, which are used in more CONSTANT:s calculated at
compile-time:
IN: iqlink.const
! Bits are rectangular, their size in pixels is here.
! All other constants are based on this one.
CONSTANT: half-bit-size 6
USING: iqlink.const ;
IN: iqlink.cell.gadget