RE: new event loop

2001-07-04 Thread Espen Harlinn
that can be found in this library could be integrated into perl, or possibly perl could be built on top of ACE. Adding support for CORBA would then be a natural extension to perl since everything else would be in place. Best regards Espen Harlinn Senior Engineer, Software Seam

RE: new event loop

2001-07-05 Thread Espen Harlinn
UG> api's will be very popular. we can do this in the perl5 event module. ACE does support async file io through the descendants of classes found in Asynch_IO_Impl.h and Proactor.h. This currently (to my knowledge) only works on Win32 platforms and on plat

Re: Final draft: Conventions and Guidelines for Perl Source Code

2001-08-13 Thread Espen Harlinn
use a coding style they are comfortable with (or close to), and run it through indent with the right set of options and it would be conformant with the upcomming guide lines. It's just a thought ... Best regards Espen Harlinn Senior Engineer, Software Seamos AS --

Are threads what we really want ???

2001-10-24 Thread Espen Harlinn
also be allowed as parameters to functions, so that a future reference variable could be passed to a function. I'm well aware that most of this functionality can be achived by other means - but I think a language and runtime level solution would be most elegant and portable. My choice of syntax and keywords are for illustration purposes only. Best regards Espen Harlinn

RE: Revamping the build system

2001-10-24 Thread Espen Harlinn
e should be kept really simple and used during the next stage of the build process to generate the final build. If a package is missing from this file, then it's not included in the final build. Best regards Espen Harlinn

RE: Revamping the build system

2001-10-25 Thread Espen Harlinn
at this is even used for. I think we need some simple way of telling the last step of the build process what's available in terms of external libraries for a given platform/compiler combination. like I might have zlib compiled with M$ VC++ and cygwin, but not with Borland C++ builder. One file for each compiler. It would also be useful to have this kind of info available when building modules later on in the process. Best regards Espen Harlinn