On Thu, Aug 17, 2000 at 05:26:18PM -0400, Sam Tregar wrote:
On Thu, 17 Aug 2000, Nick Ing-Simmons wrote:
Simon Cozens [EMAIL PROTECTED] writes:
Wow. I'm sold. Can this be how we should be doing XS in Perl 6?
So we now run equivalent of xsubpp and cc every time script is run?
No. The
On Fri, Aug 18, 2000 at 07:20:28AM +0100, Graham Barr wrote:
So it is a security issue then as it needs somewhere to cache these
object files, and anyone must be able to do it.
No more insecure than having your own LIB directory, although the prospect of
every user having their own copy of
No, because each table lookup takes less time than comparing one
letter of a text string.
sv-vtable-svpvx;
Isn't this going to really, really hurt?
--
David Nicol 816.235.1187 [EMAIL PROTECTED]
Does despair.com sell a discordian
/--- On Thu, Aug 17, 2000 at 06:17:51PM -0400, Chaim Frenkel wrote:
| Though this is a tough problem especially in the face of threads.
| Though versioned variables may be able to remove most of the
| locking
| issues and move it down into the commit phase.
Yes, but you can give
On Thu, Aug 17, 2000 at 07:01:59PM -0700, Brian Ingerson wrote:
Hi all,
This is Brian Ingerson (the Inline.pm author). My coworker, Colin Meyer,
tipped me off to this thread. I thought I'd throw in a few tidbits to
make sure everyone's on track. But first of all, make sure to RTFM.
That's the thing. It doesn't matter. It Bshouldn't matter. Keep it
pluggable; you could have everything in Latin1, in UTF8, in UTF16, or
who knows what, but the core developer shouldn't have to care. One good
way to achieve this is to have the string presented in the variable as
an array of
Oops,
In my haste to upload version 0.23 (which supports MSWin32) I introduced
a bug which will cause "make test" to fail *only* if the user is
installing Inline.pm for the first time. Of course, everyone (except me)
caught this right away.
So I hastlily uploaded v0.24 :-) Please use that one
Simon Cozens writes:
: On Fri, Aug 18, 2000 at 09:57:59AM -0700, Larry Wall wrote:
: Because we don't lose much efficiency to polymorphism, since we need it
: anyway to support generic scalars, and we gain some efficiency whenever
: we procrastinate conversions out of existence.
:
: Surely we
Perl6 RFC Librarian writes:
There has been a proposed new core function Cwant(). this seems
to be generally regarded as a good thing. Fine. If it is implemented
we should use it. Offending functions (See RFC 37) should use
Cwant() internally to determine what to return i.e; a list or a hash.
I don't think you should even attempt to version/transaction protect
a tied variable. Anything that leaves the memory or could leave the
memory (e.g. socket write) should probably not be versioned.
Unless the tied variable somehow is able to tie itself into the
transaction manager. It is up for
10 matches
Mail list logo
