>Could you please write up an RFC on this?

>K.

>On Tue, Aug 01, 2000 at 10:04:38AM -0700, Peter Scott wrote:
>>There was some discussion at TPC4 that typeglobs could be expunged from 
>>P6.  If this is likely, it would free up a type-defining punctuation 
>>character (*).
>>
>>Could this be used for filehandles?  I have often thought that filehandles 
>>were handicapped unnecesarily by looking like barewords.  Granted, these 
>>days you can put one in a scalar, but then visually, you can't tell that 
>>it's a filehandle except by context, and type prefixes are designed to 
>>obviate that problem.
>>
>>Using * as a type prefix for filehandles seems natural (it's been the most 
>>common use anyway in statements like "local *FH") and I don't see how it 
>>breaks backward compatibility any more than would happen if typeglobs get 
>>the axe.
>>--
>>Peter Scott
>>Pacific Systems Design Technologies
>>

>-- 
>Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
>Open Source development, consulting and solutions
>Level 10, 500 Collins St, Melbourne VIC 3000
>Phone: +61 3 9614 0949  Fax: +61 3 9614 0948  Mobile: +61 410 664 994

>Could you please write up an RFC on this?

>K.

>On Tue, Aug 01, 2000 at 10:04:38AM -0700, Peter Scott wrote:
>>There was some discussion at TPC4 that typeglobs could be expunged from 
>>P6.  If this is likely, it would free up a type-defining punctuation 
>>character (*).
>>
>>Could this be used for filehandles?  I have often thought that filehandles 
>>were handicapped unnecesarily by looking like barewords.  Granted, these 
>>days you can put one in a scalar, but then visually, you can't tell that 
>>it's a filehandle except by context, and type prefixes are designed to 
>>obviate that problem.
>>
>>Using * as a type prefix for filehandles seems natural (it's been the most 
>>common use anyway in statements like "local *FH") and I don't see how it 
>>breaks backward compatibility any more than would happen if typeglobs get 
>>the axe.
>>--
>>Peter Scott
>>Pacific Systems Design Technologies
>>

>-- 
>Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
>Open Source development, consulting and solutions
>Level 10, 500 Collins St, Melbourne VIC 3000
>Phone: +61 3 9614 0949  Fax: +61 3 9614 0948  Mobile: +61 410 664 994

>Could you please write up an RFC on this?

>K.

>On Tue, Aug 01, 2000 at 10:04:38AM -0700, Peter Scott wrote:
>>There was some discussion at TPC4 that typeglobs could be expunged from 
>>P6.  If this is likely, it would free up a type-defining punctuation 
>>character (*).
>>
>>Could this be used for filehandles?  I have often thought that filehandles 
>>were handicapped unnecesarily by looking like barewords.  Granted, these 
>>days you can put one in a scalar, but then visually, you can't tell that 
>>it's a filehandle except by context, and type prefixes are designed to 
>>obviate that problem.
>>
>>Using * as a type prefix for filehandles seems natural (it's been the most 
>>common use anyway in statements like "local *FH") and I don't see how it 
>>breaks backward compatibility any more than would happen if typeglobs get 
>>the axe.
>>--
>>Peter Scott
>>Pacific Systems Design Technologies
>>

>-- 
>Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
>Open Source development, consulting and solutions
>Level 10, 500 Collins St, Melbourne VIC 3000
>Phone: +61 3 9614 0949  Fax: +61 3 9614 0948  Mobile: +61 410 664 994

>Could you please write up an RFC on this?

>K.

>On Tue, Aug 01, 2000 at 10:04:38AM -0700, Peter Scott wrote:
>>There was some discussion at TPC4 that typeglobs could be expunged from 
>>P6.  If this is likely, it would free up a type-defining punctuation 
>>character (*).
>>
>>Could this be used for filehandles?  I have often thought that filehandles 
>>were handicapped unnecesarily by looking like barewords.  Granted, these 
>>days you can put one in a scalar, but then visually, you can't tell that 
>>it's a filehandle except by context, and type prefixes are designed to 
>>obviate that problem.
>>
>>Using * as a type prefix for filehandles seems natural (it's been the most 
>>common use anyway in statements like "local *FH") and I don't see how it 
>>breaks backward compatibility any more than would happen if typeglobs get 
>>the axe.
>>--
>>Peter Scott
>>Pacific Systems Design Technologies
>>

>-- 
>Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
>Open Source development, consulting and solutions
>Level 10, 500 Collins St, Melbourne VIC 3000
>Phone: +61 3 9614 0949  Fax: +61 3 9614 0948  Mobile: +61 410 664 994

>Could you please write up an RFC on this?

When in the process are we supposed to argue against this?

And why is everyone superquoting everything?

Reply via email to