Yes, shootout doesn't contain Factor currently and the
post(http://factor-language.blogspot.com/2010/05/comparing-factors-performance-against.html)
explained the reason: I'd like to submit Factor to the computer
language shootout soon. Before doing that, we need a Debian package,
and the deploy
Here are some benchmarks (posted by the author of Factor?) comparing
Factor against V8, LuaJIT, SBCL, and CPython:
http://factor-language.blogspot.com/2010/05/comparing-factors-performance-against.html
http://shootout.alioth.debian.org/ contains more benchmarks for more
programming
effect was `( -- )`. But with
\xF1, this isn't the case, and the error is thus caught.
Hope that helps,
--Alex Vondrak
On Wed, Oct 30, 2013 at 3:24 PM, OwnWaterloo ownwater...@gmail.com wrote:
I'm new to Factor and don't know how to minimize the code while get
the similar behaviour. Sorry
I have noticed this update:
https://github.com/slavapestov/factor/commit/591b1f4b72246a20111b9ea8474601f7a03d20cc
Thanks for your work, Benediktsson!
--
Android is increasing in popularity, but the open development
Hi Bertini.
After follow the information(especially the link to stackoverflow)
offered by you and some more searching and reading, I learned more
about Unicode.
First, I have had an assumption: the C in the NFC means that to
compose (or combine) some characters and the number of characters
will
I got confused after read the *Examples* section of
CHAR:(http://docs.factorcode.org/content/word-CHAR__colon__%2Csyntax.html)
:
Examples
CHAR: x
CHAR: \u32
CHAR: \u{exclamation-mark}
CHAR: exclamation-mark
CHAR: ugaritic-letter-samka
CHAR: \u{exclamation-mark} could let us input a char
I have just found that factor support \x?? in string and will
interpreter these two characters as a hex number:
IN: scratchpad \x032 array .
{ 3 50 }
But the document(http://docs.factorcode.org/content/article-escape.html)
do not mention it.
Is this escape code stable and could be used or is
*CHAR: \u??* requires six digits exactly:
IN: scratchpad CHAR: \u32 .
50
no more:
IN: scratchpad CHAR: \u032 .
1: CHAR: \u032 .
^
Assertion failed
got2
expect
Type :help for debugging help.
no less:
IN: scratchpad CHAR: \u00032 .
1:
Thanks for you reply, Bertini!
I'm also a factor newbie, much younger than you(began to use factor
yesterday in fact) :)
I got an unicode issue recently and it is the reason that I want to
have a try on *unicode.normalize* vocabulary.
The issue is that when submit a form containing a value
Sorry for out of topic. Back to Factor :)
The (nice!) documentation of Factor is in
(http://docs.factorcode.org/content/article-syntax-strings.html) and
in:
IN: scratchpad \ CHAR: help
IN: scratchpad \ help
I couldn't learn Factor so quickly with out the help of them and
really like them!
It will save me four key strokes in some situation :) Thanks!
--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
I got some experience with Factor after written some code(instead of
just read http://concatenative.org/).
The good news(to me) is that the code could be factored out more
easily in Factor and in concatenative languages in general than in
other languages, surely :)
Was the name of Factor chosen
It's true. Searing Factor language results in many *official* site:
factorcode.org, wikipedia.org, github.com/slavapestov/factor,
factor-language.blogspot.com, etc. and offers many general
information.
But for some specific task, things become worse.
For a real example which I have encountered
I think I get the idea now.
First, both exclamation-mark and ugaritic-letter-samka(as well as
x and \u32) are *concrete examples* instead of *metasyntactic
variable*(or placeholder name), am I right?
I have googled ugaritic but get more confusing... Why I couldn't
figure it out in the first
I'm new to Factor and don't know how to minimize the code while get
the similar behaviour. Sorry for that.
But thanks to the expressiveness and good libraries of Factor the code
won't be too long, I hope...
Firstly, the primary goal is to normalize some unicode string.
Formating the result will
In my personal opinion, it looks better if I could store the composed
form in different persistent storages(Darcs repository behind Gitit
wiki firstly
in which I found this issue and now Postgresql).
Decomposing the characters and then comparing them in all cases is
also an acceptable solution.
16 matches
Mail list logo
