If memory serves me right, Dan Sugalski wrote:
> >> Why would we want to avoid this? It looks exactly like what ought to
> >> happen.
If you can provide that in-vm , it would be a lot faster ...(hmm, that's
one argument that should convince you ;)
But like I said , I need lots of sticky notes
At 3:29 PM -0500 1/5/03, attriel wrote:
> At 6:56 PM +0530 1/4/03, Gopal V wrote:
If memory serves me right, Erik Bågfors wrote:
> >> would a be able to modify itself ? (unfortunately C# allows
that)
> >
To clarify here's my example ...
=cut
using System;
public struct MyStruct
{
int
At 8:43 PM + 1/5/03, Simon Cozens wrote:
[EMAIL PROTECTED] (Dan Sugalski) writes:
> I am taking the viewpoint that "everything is in object".
Then you'll likely be somewhat surprised at times.
Can you elucidate?
(I admit to be very tempted to answer this "Yes" and leave it at that...
Paul Kienzle <[EMAIL PROTECTED]> writes:
> Piers Cawley wrote:
>
>>* Thanks to everyone who has given me feedback as a result of these
>>summaries. It's really good to know that people finding these things
>>useful.
>>
> Me too. I find I no longer read the list because I c
[EMAIL PROTECTED] (Dan Sugalski) writes:
> > I am taking the viewpoint that "everything is in object".
>
> Then you'll likely be somewhat surprised at times.
Can you elucidate?
--
Ah the joys of festival + Gutenburg project. I can now have
Moby Dick read to me by Stephen Hawking.
> At 6:56 PM +0530 1/4/03, Gopal V wrote:
>>If memory serves me right, Erik Bågfors wrote:
>>> > >> would a be able to modify itself ? (unfortunately C# allows
>>> that)
>>> > >
>>
>>To clarify here's my example ...
>>
>>=cut
>>
>>using System;
>>public struct MyStruct
>>{
>> int val;
>>
On Fri, 3 Jan 2003, Dave Whipp wrote:
> John Williams wrote:
>
> > Do they? One is obviously an array, and one is obviously a scalar.
> > You may get an error (cannot alias an array as a scalar) or $b get aliased
> > to the array-in-scalar-context (a reference).
>
> This is one of those "how we th
At 6:56 PM +0530 1/4/03, Gopal V wrote:
If memory serves me right, Erik Bågfors wrote:
> >> would a be able to modify itself ? (unfortunately C# allows that)
> >
To clarify here's my example ...
=cut
using System;
public struct MyStruct
{
int val;
public MyStruct(int x){ val=x; }
public
At 1:19 PM -0800 1/3/03, Dave Whipp wrote:
I am taking the viewpoint that "everything is in object".
Then you'll likely be somewhat surprised at times.
--
Dan
--"it's like this"---
Dan Sugalski
>> If I have "0", it's possible I might at some point (this having been
>> user input perhaps) have some reason to care whether it was an integer
>> or a string.
>
> How would the user distinguish when providing the input? The Perl 5
having slept now, the same thought occurs to me ... I think I w
[EMAIL PROTECTED] (Dave Whipp) writes:
> am taking the viewpoint that "everything is in object". A number is an
> object; an array is an object, a hash is in object. The only thing
> that differs is that they implement different interfaces.
>
> Perl6 provides syntaxes for those interfaces. $a and
Piers Cawley wrote:
* Thanks to everyone who has given me feedback as a result of these
summaries. It's really good to know that people finding these things
useful.
Me too. I find I no longer read the list because I can pick up the few
relevant bits from the summary
and fo
I'm not willing to go so radically to start, but I did have an idea.
I think part of the extra cost is just in cache fluffiness--the sync
info just isn't being used much. I don't think that it, or the
property info, will be used most of the time. We could yank the
metadata and sy
John Williams wrote:
Do they? One is obviously an array, and one is obviously a scalar.
You may get an error (cannot alias an array as a scalar) or $b get aliased
to the array-in-scalar-context (a reference).
This is one of those "how we think about the fundamentals" things. I am
taking the v
Mitchell N Charity wrote:
(3) A new reflector/reference class.
void set_integer_native (INTVAL value) {
PMC *object_reflected = SELF->cache.pmc_val;
object_reflected->vtable->set_integer_native(...);
}
Question ONE - What parts of the above code, if any, need to be
changed
[EMAIL PROTECTED] (Murat Ünalan) writes:
> I have a german background. But my litte english-vs-perl6 example sounds
> not so odd to me (what doesn't mean to much):
>
> my ( john, james, jim, tony ) are
> ( 102, 99,88, 79 )
Actually, I think thi
> or as useful as:
>
>my DNA %sequence is human size(4) =
>(alpha => 'atgc', beta => 'ctga', gamma => 'aatt',
> delta => 'ccaa'_;
oh , this is damn *PERFECT* !
a) easy reading
b) 'type' and 'property' adjacent without hopping through list
of varnames or complex prope
Attriel wrote:
> Well, in general I think it would be good to have some mechanism for
> determining the type of the data rather than the type of a
> representation of the contained value.
Why? One of the nice things about Perl is that coercian takes care of
these kind of things so that you don't
18 matches
Mail list logo
