It shouldn't be a problem. *_ would then be a 'special' reserverd identifier. *_name could be a named placeholder. <chaim> >>>>> "JH" == Jeremy Howard <[EMAIL PROTECTED]> writes: JH> John Porter wrote: >> Has anyone suggested '*'? Since its use for typeglobs is (repsumably) >> going away, it's available (right?). >> >> It the "wildcard" mnemonic value is consistent with "placeholder". >> JH> Yes, it's been suggested, but we might be too late on that one--another RFC JH> suggests reserving '*' for reserved perl identifiers. JH> - *: Next best, if not used to signify perl reserved identifiers -- Chaim Frenkel Nonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183
- Re: Different higher-order func ... Nathan Wiger
- Re: Different higher-order func ... Bart Lateur
- Re: Different higher-order func ... Jeremy Howard
- Re: Different higher-order func ... Jeremy Howard
- Re: Different higher-order func ... Nathan Wiger
- Re: Different higher-order func ... Nathan Wiger
- Re: Different higher-order func ... Bart Lateur
- Re: Different higher-order func ... John Porter
- Re: Different higher-order func ... Jeremy Howard
- Re: Different higher-order func ... Peter Scott
- Re: Different higher-order func ... Chaim Frenkel
- Re: Different higher-order func notat... Damian Conway
- Re: Different higher-order func notation? (wa... Ken Fox
- Re: Different higher-order func notation?... Jeremy Howard
- Re: Different higher-order func notation? (was Re... Peter Scott
- Re: Different higher-order func notation? (was Re... Bart Lateur
- Re: Different higher-order func notation? (wa... Jonathan Scott Duff
- Re: RFC 23 (v1) Higher order functions Ken Fox
- Re: RFC 23 (v1) Higher order functions Damian Conway