ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> perl6-language
perl6-language
Re: BEGIN {...} and IO
by Nicholas Clark other posts by this author
Aug 13 2005 8:28AM messages near this date
Re: BEGIN {...} and IO | Re: BEGIN {...} and IO
On Tue, Jun 14, 2005 at 07:56:32PM +0200, Ingo Blechschmidt wrote:
>  Maybe we should just hardcode the filehandles-leaking-into-runtime case
>  in the compiler? And, if the compiler can't detect the problem at
>  compile-time, just throw a runtime exception?
>  
>      my $fh = BEGIN { open "some_file" };
>      =$fh;  # "Can't readline() on unopened filehandle leaked
>             # from compile-time into runtime, try to..."
>  
>  Opinions?

Aren't filehandles just part of a more general case of the compiler
serialising something out to the bytecode on disk that can't actually be
serialised? So the attempt at serialisation of a file handle, directory
handle, database handle, shared memory handle or any other external resource
should fail? (Unless that resource class has a viable serialise/deserialise
system)

Nicholas Clark
Thread:
Ingo Blechschmidt
Nicholas Clark
Ingo Blechschmidt
Yuval Kogman

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved