Hey guys,
I got to thinking about how factor git won't bootstrap on freebsd (and
has been in this state for a while), and I'm wondering if we don't
have too many modules loaded during bootstrapping. Could we at least
remove the new code from the boot stages until it is fixed for other
OSe
Hi Stephen,
Take a look at the 'lines' word (type '\ lines help' in your listener). This
will give you a sequence of strings, which you can then use { "XX" }
split on to get the separate parts of the data. Factor's sequences
vocabulary is amazingly useful. Remember that strings are sequences i
Sounds like it would make a great homework problem.
I'd consider using 'sort' on the characters of each word, because that
changes ANY scrambling to the same form. I'd also consider using a
hashtable instead of a simple vector.
-Wm
Hey guys,
I was starting to get into the Factor programming language and I have never
done any programming in this language. I have done some programming in
Scheme so I have some knowledge about how some of the syntax works in this
language, but there are several differences. My question comes
You're right, and I agree that replacement characters are a better
default than throwing errors.
But with replacement characters, having a UTF8 default with no
indication that it is UTF8 would lead to confusion among newbies
attempting to read binary files. If they write "foo.jpg"
and it give
> This is only a one-time thing however, once a programmer learns about
> encodings and the default being utf8 they're not likely to make that
> mistake again. Also I believe you mentioned that the probability of
> random binary data decoding as valid utf8 is low; so chances are they'll
> get
Eduardo Cavazos wrote:
> {
> "[EMAIL PROTECTED]"
> "[EMAIL PROTECTED]"
> "[EMAIL PROTECTED]"
> } builder-recipients set-global
That's the Factor cabal, responsible for making sweeping language
changes and implementing major features in total secrecy :-)
As soon as I get around to it, I'll c
Matthew Willis wrote:
> This may not be necessary, but I had an idea today about having other,
> remote machines be able to participate in the build farm. A remote
> tester could set up a daemon on their own machine that would perform
> the same tests that are in your build farm. Even if those
Oh man, that sounds awesome!
This may not be necessary, but I had an idea today about having other,
remote machines be able to participate in the build farm. A remote
tester could set up a daemon on their own machine that would perform
the same tests that are in your build farm. Even if th
Matthew Willis wrote:
> Hey guys,
>
> Due to some recent changes, factor no longer bootstraps on FreeBSD.
> The problems are coming from unix.stat, which has backends for OS X
> and Linux only. Is there a way for other architectures to opt out?
There's no way to "opt out", but in fact what's
Hey guys,
Due to some recent changes, factor no longer bootstraps on FreeBSD.
The problems are coming from unix.stat, which has backends for OS X
and Linux only. Is there a way for other architectures to opt out?
Thanks!
Matt
Hello,
'open-log-stream' uses ascii for creating the log:
: open-log-stream ( service -- stream )
log-path
dup make-directories
1 log# ascii ;
Americans only need apply?
The 'logging.insomniac' vocabulary expects 'utf8' data.
Ed
---
> how should byte array streams taken an encoding?
They don't take an encoding from the stack. You set the encoding.
GENERIC: ascii ( object -- object )
M: path ascii ( path -- path ) \ ascii >>encoding ;
M: stream ascii ( stream -- stream ) \ ascii >>encoding ;
13 matches
Mail list logo
