On Aug 31, 2008, at 6:35 PM, Joe Groff wrote:
> On Aug 31, 2008, at 5:27 PM, Slava Pestov wrote:
>
>> Hi Joe,
>>
>> This problem has been fixed. I have tested the deploy tool with a
>> few simple examples and the unit tests pass. Let me know if you
>> have any other problems.
>
> Man, what ser
On Aug 31, 2008, at 5:27 PM, Slava Pestov wrote:
> Hi Joe,
>
> This problem has been fixed. I have tested the deploy tool with a
> few simple examples and the unit tests pass. Let me know if you have
> any other problems.
Man, what service! Thanks, Slava. I tried deploying a few demos, and
Ed wrote:
> One: throw a parse time error if more than one used vocabulary exports the
> same name which is in turn used by the using vocabulary.
Maybe the way to proceed is to turn on this check and see what happens to the
codebase. :-)
Let's suppose that a vocabulary is changed which triggers
Hi Joe,
This problem has been fixed. I have tested the deploy tool with a few simple
examples and the unit tests pass. Let me know if you have any other
problems.
Slava
On Sun, Aug 31, 2008 at 12:51 PM, Joe Groff <[EMAIL PROTECTED]> wrote:
> I was trying to deploy an image, and the resulting ap
I've also hit this problem a few times and it's difficult to track
down. If there were a parse time error it would be easier.
If I change peg for example to add a new word that shadows something
in a users vocab, that user would probably like to know straight away
when they next update via a 'reso
Slava Pestov wrote:
> You won't have to resolve words you don't use.
OK that's good. Then disregard the email that's on the way. :-)
Ed
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build th
Slava wrote:
> Let me again propose the feature where if you have a:foo and b:foo, then
> USING: a b ; foo, you get a parse time error about ambiguity in the search
> order.
We currently have ways to address the problem. For one, there is no ambiguity
because the USING: order determines which on
You won't have to resolve words you don't use.
Suppose you have two words, a:foo and b:foo. You will be able to do
USING: a b ;
IN: my-vocab
Without further qualifications, as long as you don't refer to 'foo'.
You'll only have to RESOLVE: a/b foo if you refer to 'foo'. The other
alternative wou
Slava wrote:
> Let me again propose the feature where if you have a:foo and b:foo, then
> USING: a b ; foo, you get a parse time error about ambiguity in the search
> order.
What happens if the vocabulary using 'a' and 'b' doesn't refer to 'foo'? Will
the error occur?
That would be mighty annoy
I didn't see any compiler errors when I added the 'ALIAS: second
seconds' to calendar. In fact, Factor didn't even throw the popup
exception until I bootstrapped again. I could have been using the
same image for a few more days and made lots of commits before ever
having to bootstrap agai
On Sun, Aug 31, 2008 at 6:16 PM, Eduardo Cavazos <[EMAIL PROTECTED]>wrote:
> Let's say vocabularies X Y Z use vocabulary A. I edit A. I refresh-all.
> Let's
> suppose that 'refresh-all' has the proposed behaviour whereby it refreshes
> X
> Y and Z since they depend on A (I believe you mentioned th
Moving this to 'factor-talk' so others can chime in. You give a good enough
description below so that others can catch up.
Slava wrote:
> We figured this out. Doug added a 'second' word to calendar which shadowed
> sequences:second in ui.gestures.
>
> This took me 5 minutes to bootstrap and anot
I have used curry but I haven't fry and I don't know what fry does ...
but looking at the two examples you posted ... fry versions look
strange to me. this is just "looks" based oppinion.. take it as so..
btw and OT ... I am upgrading my company and I renamed it to REFAKTOR
LTD ... your little pes
I am not at my factor computer so can't try it right now , but will tomorrow.
refactr? these web 2.0 names are really science of it's own :) they
have a db error on their page.
I have to call it refaktor because we can't have company names with
english words ... it's just a company name... my "we
Entering ``"fry" about'' in the listener will explain what it's all about.
And FWIW, there is already a ``Web 2.0'' startup named REFACTR:
http://refactr.com/ :-)
Slava
On Sun, Aug 31, 2008 at 5:52 PM, janko metelko <[EMAIL PROTECTED]> wrote:
> I have used curry but I haven't fry and I don't kn
Slava wrote:
> fry cannot express 'with' so we wouldn't do anything about usages of that
> word.
Dan wrote:
> > I'm not sure how to do what "with" does in terms of fry.
10 { 0 1 2 3 4 } [ - ] with map
Using fry:
10 { 0 1 2 3 4 } swap '[ , _ - ] map
I'm not saying it's pretti
Hi Dan,
Yes, that is what I'm suggesting. fry cannot express 'with' so we wouldn't
do anything about usages of that word.
Thanks for the input. I'll probably do a sweep of my own code at some point
to convert curry/compose to fry, since I find fry more aesthetically
pleasing, but I'll let other c
Well, personally, I never got used to fry. I feel comfortable using
curry and compose for most things. I don't see why it is a problem to
use them except in exceptionally complicated cases. For me, it feels
like fry is doing more than is needed. Are you suggesting that we use
{ 1 2 3 } 4 '[ , + ]
Hi Joe,
I know about this. As a workaround, enable 'retain C types' in the deploy
tool.
The problem is that code like "int" heap-size isn't constant-folded, because
folding of calls to generic words is broken. There will be a fix coming up
shortly.
Slava
On Sun, Aug 31, 2008 at 12:51 PM, Joe Gr
I was trying to deploy an image, and the resulting app is bombing out
with a "no-c-type" exception inside a call to . Now it's no
big deal to switch on "deploy-c-types?", but looking at the definition
of in core-foundation, it seems like it shouldn't need the
c-types at runtime:
GENERIC:
20 matches
Mail list logo
