Re: [Factor-talk] how can I suppress 'literal expected' warnings?

2009-02-27 Thread Slava Pestov
On Sat, Feb 28, 2009 at 1:39 AM, Jong-Hyouk Yun wrote: > ps. on Win32, same source generated "alien-invoke-error", > "CreateFileW". but now it loading just fine. :-) Yeah, the error handling is sub-optimal here. Soon the situation will improve. Inference warnings will go away and inference errors

Re: [Factor-talk] how can I suppress 'literal expected' warnings?

2009-02-27 Thread Jong-Hyouk Yun
Thanks, Slava! commit cf6a12c55cdc81454f1bb06e69d2ddc3167fbe54 Author: Yun, Jonghyouk Date: Sat Feb 28 16:29:25 2009 +0900 io.encodings.korean johab, cp949 => encode-char refactoring... ps. on Win32, same source generated "alien-invoke-error", "CreateFileW". but now it loading just fine

Re: [Factor-talk] how can I suppress 'literal expected' warnings?

2009-02-27 Thread Slava Pestov
Hi, If you get this error at parse time (as opposed to in a :warnings list), it means that you made a word that's supposed to be optimized (like an I/O word, sequence word, etc) fail to have a static stack effect and therefore not optimized. If you wrote a combinator, make sure it is declared inl

[Factor-talk] how can I suppress 'literal expected' warnings?

2009-02-27 Thread Jong-Hyouk Yun
Hi, I'm working on "io.encodings.korean" support Johab encoding and refactoring "cp949", "johab" => encode-char/decode-char's common patterns. here is my personel github: http://github.com/ageldama/factor/tree/master I want remove duplicated codes in my cp949/johab encodings and no need to load

[Factor-talk] Pull request: FUEL: persistent listener history

2009-02-27 Thread Jose A. Ortega Ruiz
FUEL's listener keeps an input history, which you can access, for instance, with M-p, M-n. But, up to know, when you killed the listener's buffer, the history was lost. The patch below makes history persistent; up to `fuel-listener-history-size' entries (150 by default) are kept in a file with pat