Sorry Jim, I missed some nuances of your questions the first time  
around. I'll try to fill in the blanks.

On Nov 7, 2009, at 2:25 PM, Jim mack wrote:

> 1)  CHAR: \space <string> is missing \space.
>     a) Of course CHAR: 32 <string> works, but it seems we avoid  
> this.  What is better way?
>     b) Closest I can come is command-writer.factor, which has a  
> CHAR: space write1.  I can't figure out where space is defined.  I  
> think I looked (but obviously missed it) in each file in USING: io  
> io.crlf kernel math.parser sequences strings interpolate locals ;   
> and browser is not helpful.  What techniques are there to start from  
> command-writer & find out where it thinks it's getting the word from?

If you look at the docs for CHAR: 
(http://docs.factorcode.org/content/word-CHAR__colon__%2Csyntax.html 
), it says CHAR: takes a literal character, an escape code, or a  
Unicode character name. «CHAR: space» is using the Unicode character  
name for the space character. The Unicode character data is read from  
basis/unicode/data/UnicodeData.txt when the Unicode library is compiled.

> 2)  finding conflicts for TYPEDEF: short XXX.
>     a) says between alien.c-types & sequences
>     b) I read the latter should win in USING: but this doesn't seem  
> to apply

That's how it used to be, but we've since implemented a more robust  
namespacing scheme documented in the article I linked you from my  
first email. Could you tell us where you read that from in the docs so  
we can update them?

>     c) I read syntax << "alien.c-types" xxx >> would help, but can't  
> find that article now, and couldn't figure out exact syntax at the  
> time.

Not sure where you got that from. << >> is just used for parse-time  
evaluation. Again, if you could point out where in the docs you read  
this so we can clarify it for future new users, that'd be helpful.

> 3)  Use of >r r>
>     c) is there a better temp stack technique?

The temporary stack in Factor has been relegated to an implementation  
detail. The dip combinators 
(http://docs.factorcode.org/content/article-retainstack-combinators.html 
) are the preferred way in Factor for temporarily stashing values,  
since they enforce balanced use of the temporary stack and tend to be  
more readable.

-Joe
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk

Reply via email to