different parts of the file (one
to the zip archive, another to the unarchiver).
And how is this going to interact with "-T" or whatever we're going to use?
Under my suggested scheme, the data would be untainted if it's covered by a
verified signature, and tainted if not.
-Martin
file? Or a new name E which it will refer to?
And do all the above without requiring A and C to be in the same directory?
I would strongly recommend deprecating any distinction between "volume" and
"path", and instead provide functions which focus on allowing us to answer
On Thu, 4 Sep 2003 [EMAIL PROTECTED] wrote:
> On Mon, 1 Sep 2003, Michael G Schwern wrote:
> > You also must worry about volumes.
[my long explanation snipped]
Sorry, wrong list; this is a standard-module issue, not an implementation
issue or even a core-language issue.
-Martin
count clock drift, while "system elapsed
time" is left unaffected. Which you want depends on whether you want to
sleep for a specific time, or wake up at a specific time, and it would be
nice if Parrot didn't rule out making use of that.
-Martin
13,17],
and a concatenation iterator over those. Whether the iterator over [2] is
created over a singleton array or directly from the scalar would seem to be
simply a matter of economy.
-Martin
On Tue, 7 Sep 2004, Leopold Toetsch wrote:
> > [*] Unless it's a _feature_ that given tied $a,
> >($a = "aaa") =~ s/a/b/g
> > would call STORE four times ("aaa", "baa", "bba", "bbb").
>
> I'd expect two stores here. One for the initial setting of the value and
> one for the final result
;) =~ s/a/b/g>.
I would agree with you in general, but since we're generally after speed,
surely we want to allow for optimisations such as "don't store unless
something's changed"; this would also be compatible with the boolean context
value of s///.
-Martin
--
CAUT
" (native) method to
each integer register, which could implement the required logic for each of
the above cases? Or would we need perhaps a vtable, with both "store" for
when we're interpreting, and "generate_jit_store" for when we're jitting?
-Martin
string? Then you wouldn't have
to generate extra temporary strings to hold the concatenations, but where
you did have a string that included the appropriate sigil, it could be used
directly by having an empty prefix.
-Martin
le generation aborts (probably due to an empty
PMC list) - I'm looking into it.
cu,
Martin
--
O Lord, won't you buy me | Martin Vorlaender | OpenVMS rules!
an HP OS | work: [EMAIL PROTECTED]
its name starts with "Open" | http://w
en it's good enough
to be published.
That said, it was a relatively painless port so far.
Thanks to all who wrote the configuration scripts with portability in mind.
cu,
Martin
[1] for a make/MMS comparison, please see
http://vms.pdv-systeme.de/users/
ot';'bar']
2. if myHLL does not actually define ['myHLL';'foo'] but then checks to
see if it's usable, and would find ['parrot';'foo'] via the normal
inheriting framework.
But how often are these actually likely to be the case, and are there
any other cases?
-Martin
7;t talking about *that* namespace.
-Martin
nclosing dynamic scope that catches it and
transmogrifies it into an Uncaught Exception?
Or if not, could we have both back-traces available? A "created_by" back-trace
and a "thrown_by" back-trace?
-Martin
we should if possible allow an
extensible type system, possibly including optional automatic promotion to a
library-implemented integer type (BigNum, Complex, or whatever).
-Martin
(I find it quiet disappointing that "modern" languages like Java and C# rely
entirely on storage-b
lling how healthy that bytecode is.
exit(EXIT_FAILURE); // 1 on most platforms
-Martin
--
CAUTION: The information contained in this message is consequential and
subject to legacy provenance. If you are the intended recipient you are
hereby notified that reading this message is permitted. If
On Wed, 23 Oct 2002, Rhys Weatherley wrote:
> Martin D Kealey wrote:
> > [Frank Farance's paper] "specification based extended integer range"
> > [at] http://wwwold.dkuug.dk/JTC1/SC22/WG14/docs/c9x/extended-integers/.
> Very interesting proposal. I wish they ha
etween threads -- but of course, that is only sensible
because it is not even shared between multiple closures *within* a thread.
-Martin
t row objects. And when the
transaction goes out of scope it needs to be either committed or rolled
back.
-Martin
On Thu, 28 Apr 2005, Luke Palmer wrote:
> Or, with the "block hooks" that I keep claiming makes timely destruction
> almost never needed, it is:
>
> {
> my $s = new CoolClass;
> # ... do stuff that may throw ...
> LEAVE { destroy $s }
> }
>
> This destroys properly a
ing in a good direction on
> concurrency stuff at a language level too.
So can we look towards having things like "map" and "grep" be parallel (or
at least unordered) by default?
-Martin
whole records, or lines of text,
or whatever.
Clearly this needs to be discussed in p6-lang, but having separated the
two parameter types, the filter can decide which it can implement, and
how.
-Martin
27;t.
Any reason to treat HLL namespaces differently from classes, at least in
respect of being an inheritance hierachy? Simply make 'yourHLL' inherit from
'parrot', and the rest follows...
-Martin
23 matches
Mail list logo
