> Ed has proposed some stack effect changes to core collection words and
> Dan is toying with generic collection protocols but I'm still undecided
> as to whether these ideas are worthwhile, and if adding them now will
> postpone 1.0 too far. Perhaps both can be merged into one proposal: a
> g
Phil Dawes wrote:
> One of the things I'm loving about factor is its ability to change
> implementation direction on a sixpence. I don't know how long this can
> last, but for now it's a massive plus for the language.
This came up on the IRC channel today. Factor is changing quickly and a
lot o
Daniel Ehrenberg wrote:
> I don't understand how this will interact with byte array readers,
> sockets and other kinds of streams which don't have paths as such. I
> don't see how it could be any different from how things are right now,
> unless you want to generalize paths significantly. Unless th
I don't understand how this will interact with byte array readers,
sockets and other kinds of streams which don't have paths as such. I
don't see how it could be any different from how things are right now,
unless you want to generalize paths significantly. Unless this
generalization (which I don't
Eduardo Cavazos wrote:
> In the api that I'm proposing, the examples you give above still look
> like
> this:
>
> iso-2022-jp
>
> shift-jis
>
> How is that "harder" than the current api? It's in fact identical.
Ed, your "smart pathname" proposal has two distinct parts. The first
pa
Alex Chapman wrote:
> I actually quite like the idea of having to explicitly state what encoding I
> want to read or write a file in.
Here's the current system:
"data" utf8
In the api I'm proposing you can do:
"data" utf8
I agree that you should be able to explicitly state
Matthew Willis wrote:
> I REALLY don't want working with the various formats I work with to
> become any harder than it already is. I do not want to sacrifice the
> ease of saying 'iso-2022-jp ', 'shift-jis ',
> and all the other adorable encodings japanese people like to use.
In the api t
William Tanksley, Jr wrote:
> I feel really stupid ... I tried to look up to verify
> how to properly apply it (specifically, I wanted to look up the right
> conventions for naming things like set-codec; I'm a newbie), and I
> simply can't find it in the Vocabulary. What's under? I *expected* it
>
Alex Chapman <[EMAIL PROTECTED]> wrote:
> Hi William,
> William Tanksley, Jr <[EMAIL PROTECTED]> wrote:
> > I feel really stupid ... I tried to look up to verify
> > how to properly apply it (specifically, I wanted to look up the right
> > conventions for naming things like set-codec; I'm a newbie
Hi William,
On 11/03/2008, William Tanksley, Jr <[EMAIL PROTECTED]> wrote:
>
> I feel really stupid ... I tried to look up to verify
> how to properly apply it (specifically, I wanted to look up the right
> conventions for naming things like set-codec; I'm a newbie), and I
> simply can't find it
Slava Pestov <[EMAIL PROTECTED]> wrote:
> William Tanksley, Jr wrote:
> > What if binary were the default, but different filters could be
> > attached to a binary stream to modify how it behaved?
> That's how Dan's API is implemented internally right now.
> It could be renamed to or something
William Tanksley, Jr wrote:
> What if binary were the default, but different filters could be
> attached to a binary stream to modify how it behaved?
That's how Dan's API is implemented internally right now.
"foo.txt" utf8
is equivalent to
"foo.txt" (file-reader) utf8
(file-reader) is the pla
Eduardo Cavazos <[EMAIL PROTECTED]> wrote:
> No matter what, this is a fact: we are going to have a world-class unicode
> implementation. I know this because Dan knows his stuff and I trust him to
> solve problems like this.
Frankly, his blog is excellent reading; you will at the very least
und
Well, on my Safari pulldown menu there are:
Shift JIS X0213
ISO 2022 JP
Shift JIS
EUC
If you know just one Japanese word, it should probably be
http://en.wikipedia.org/wiki/Mojibake
:)
Matt
On Monday, March 10, 2008, at 02:35PM, "Daniel Ehrenberg" <[EMAIL PROTECTED]>
wrote:
>IIRC ISO 2202 J
IIRC ISO 2202 JP = Shift JIS (unless that's referring to the Microsoft
extension). But that's a little irrelevant here...
Dan
On Mon, Mar 10, 2008 at 7:36 AM, Matthew Willis <[EMAIL PROTECTED]> wrote:
> I REALLY don't want working with the various formats I work with to become
> any harder than i
Matthew Willis wrote:
> Hey! I'd love to give it a shot. And, won't we need to revive the ARM
> port for use on iPhone? :)
Unfortunately the iPhone SDK has some pretty ridiculous restrictions --
you can only distribute your programs through the Apple store, and
you're not allowed to write progr
On Monday, March 10, 2008, at 02:12PM, "Slava Pestov" <[EMAIL PROTECTED]>
wrote:
>Matthew Willis wrote:
>> Ed,
>>
>> I work with different encodings of Japanese, and it's a big headache.
>> The biggest part of the headache is that no one knows what encoding
>> they are using when they make fil
Matthew Willis wrote:
> Ed,
>
> I work with different encodings of Japanese, and it's a big headache.
> The biggest part of the headache is that no one knows what encoding
> they are using when they make files. So, you see garbled web pages
> because the encoding wasn't specified in headers or
Eduardo Cavazos wrote:
> Let's assume the newbie is living in mandatory encoding parameter land.
> The newbie, being a typical newbie, learned about by seeing it
> used in some code. He saw "..." utf8 .
>
> Statistically speaking, based on encoding distributions, he is most
> likely to
>
Hi Ed,
I originally thought the the extra argument to file-reader/writer was
going to be a pain but now I'm warming to the idea. I've come across
two places in my code where I thought I'd be using a utf-8 encoding but
actually I need to load using binary and then do the conversion later.
My vote
Hi All,
This reminds me of the first C program I ever wrote as a freshman in
college working at ARL in 2000. I had to download a waveform from a
file to an arbitrary waveform generator (arb) for work. http://
tinyurl.com/2ga8g3
With my trusty Schaum's Outline of Programming with C and a ru
Eduardo Cavazos <[EMAIL PROTECTED]> wrote:
> Text is the default
Text is the convenient default; it'll be used more often.
But text is also the *destructive* option -- it'll munge input and
output, unpredictably and without warning. I'd like to open a little
discussion for the possibility
Ed,
I work with different encodings of Japanese, and it's a big headache.
The biggest part of the headache is that no one knows what encoding
they are using when they make files. So, you see garbled web pages
because the encoding wasn't specified in headers or was specified
incorrectly,
Hey Ed,
I don't feel as strongly about this as you seem to, but I actually quite
like the idea of having to explicitly state what encoding I want to read or
write a file in. Otherwise it just seems to be 'programming by coincidence'
when the default of utf8 happens to be what you wanted. I don't wa
Guys,
No matter what, this is a fact: we are going to have a world-class unicode
implementation. I know this because Dan knows his stuff and I trust him to
solve problems like this.
However, there's the implementation and then there's the api.
I just wanted to point out and emphasize in case s
Slava wrote:
> 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.
In my last response, I covered the case where a newbie, having some of the
hacker spirit in him, learned of in the
Slava wrote:
> 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.
Let's assume the newbie is living in mandatory encoding parameter land.
The newbie, being a typical newbie, learned
Stephen,
OK, there is essentially one problem to solve in your homework assignment. You
have a list of words, and the list of scrambled words. For each scrambled
word, you want to see how many words it can "match". The number of words it
can match is zero or more.
I think you'll have earned yo
Thanks!
And, with the new build system I'm sure it will be easy to find/fix
these problems in the future!
Matt
On Mar 10, 2008, at 12:16 AM, Slava Pestov wrote:
> Matthew Willis wrote:
>> Hey guys,
>>
>> I got to thinking about how factor git won't bootstrap on freebsd
>> (and
>> has been i
Matthew Willis wrote:
> 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
30 matches
Mail list logo
