Glad to see someone heeded that warning about unrecognizable sarcasm;
no danger of misinterpretation here . . . :)
On 2003-01-16 at 10:01:04, Michael Lazzaro wrote:
> Well, I don't know about anyone else, but *I'm* planning on making
> many, many Unicode synonyms, to make my code shorter and more
On 2003-01-16 at 16:42:15, Buddha Buck wrote:
> [Note: I originally sent this to Mr. Nobody alone, but that wasn't my
> intent. I'm re-sending it here, where I wanted it to go in the first
> place. -- bmb]
This came in with a content type text/plain, charset=us-ascii.
US-ASCII is by definition 7
On 2003-01-17 at 19:00:04, Simon Cozens wrote:
> This is plainly untrue. See the "perlsub" documentation, which talks about
> "creating your own syntax" with the & prototype. You can do all this in
> Perl 5, and it saddens me that some of the people redesigning Perl don't
> know what Perl can do.
W
On 2003-01-17 at 14:15:46, I wrote:
> But as I see it, the real problem being solved by the new syntax
> is that grep and map can exist solely as methods on some class
> in the inheritance tree of @arrays, no global functions required.
> That is a Good Thing.
I realize that such also be true if w
On 2003-01-17 at 17:17:03, Joseph F. Ryan wrote:
> >But as I see it, the real problem being solved by the new syntax
> >is that grep and map can exist solely as methods on some class
> >in the inheritance tree of @arrays, no global functions required.
> >That is a Good Thing.
> >
>
> In your op
On 2003-01-21 at 11:09:21, Thom Boyer wrote:
> One of the most... er, *interesting*, dodges I've seen in this area is the
> one used by Squeak (a Smalltalk variant). Squeak spells assignment with an
> underscore ("_"), but the Squeak system *draws* it as a left-pointing arrow.
There's a history beh
On 2003-01-29 at 09:44:27, Aaron Sherman wrote:
> Yes, I would expect that. In my opinion there is no difference between
> an array and a hash other than the underlying storage and the
> type-management of the key.
Perhaps it is your opinion that those should be the only differences,
but the actua
On 2003-01-29 at 10:32:58, Mark J. Reed wrote:
> (What their value should be is the subject of the
> parallel thread on array defaults).
Whups, that would be THIS thread, actually. The sidebar on
removing the syntactic distinction between arrays and hashes
made me think I was over in the
On 2003-02-07 at 11:13:07, Austin Hastings wrote:
> --- Michael Lazzaro <[EMAIL PROTECTED]> wrote:
> > I'm trying, and failing, to accurately and definitively answer the
> > question "what's the difference between an array and a list in
> > Perl6?"
>
> How's this?
>
>
> A list is a
On 2003-02-07 at 14:26:42, Mark J. Reed wrote:
> Not really, though. A list can be an lvalue, provided it is a list
> of lvalues:
>
> ($a, $b, $c) = 1,2,3;
Forgot the parens on the right side, there:
($a, $b, $c) = (1,2,3);
> But they certainly aren't lvalu
On 2003-02-07 at 12:18:21, Austin Hastings wrote:
> > Although this may reasonably be regarded as a special case; you
> > certainly can't pop a list:
> >
> > (1,2,3).pop => error
>
> But could you do it the other way (function instead of method)?
> pop (1,2,3) => ?
Nope. At least, n
On 2003-02-11 at 17:12:52, Joseph F. Ryan wrote:
> > (@a,@b,@c).pop
>
> This doesn't make any sense, since pop modifies the pop-ee.
> What do you expect should happen here?
>
>
> >
> > [@a,@b,@c].pop
>
>
> Same as above.
Except that the Perl5 equivalent, ugly as the syntax may be, works
On 2003-02-11 at 17:44:08, Mark J. Reed wrote:
> pop @{[@a,@b,@c]}
>
> It creates an anonymous array, then removes the last element, leaving two
> elements in the array - which is irrelevant since the array is
> then discarded completely.
Minor correction: we don&
[Recipients trimmed back to just p6-language; the Cc: list was getting
a bit large.]
On 2003-02-11 at 12:56:45, Garrett Goebel wrote:
> I'd just stick with Uri's explanation. Arrays are allocated. Lists are
> on the stack...
Nuh-uh. Those are implementation details, not part of the language
defin
On 2003-02-11 at 16:52:36, Dave Whipp wrote:
> "Mark J. Reed" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> >
> > On 2003-02-11 at 17:44:08, Mark J. Reed wrote:
> > > pop @{[@a,@b,@c]}
> > >
On 2003-02-12 at 11:07:45, Joseph F. Ryan wrote:
> Meaning that "I think this should be possible, but I'm not
> sure if that syntax is correct, because it would mean that
> the arrayrefs would need to be their own class to allow
> a method to be called on it.
No, they wouldn't, unless I'm missing s
On 2003-03-10 at 18:03:12, Uri Guttman wrote:
> this confuses me. sometimes i want a simple pass by value param which i
> can modify locally in the sub. is this the same as the constant above?
No, that's the same as "is copy".
--
Mark REED| CNN Internet Technology
1 CNN Cente
On 2003-03-11 at 10:12:17, Damian Conway wrote:
> Austin Hastings wrote:
>
> >It is explicitly stated that "is rw" on a slurpy parameter distributes
> >across all the components.
> >
> >Is there some way of differentiating array of const vs. array of rw?
> >
> >That is, creating a hash or array t
On 2003-03-13 at 05:44:09, Damian Conway wrote:
> >2- Yeah! ... umm, are we *paying* you for this?
>
> Not any more. In fact, like Larry and several others on the design team,
> I'm now paying for the privilege of doing it. ;-)
If the TPF isn't supporting you folks anymore, what's the best
way fo
On 2003-06-16 at 17:48:58, Simon Cozens wrote:
> % grep printf cvs/modules/**/*pm | wc -l
> 15
> % grep -v printf cvs/modules/**/*pm | wc -l
> 15360
>
> Well, 0.1% agreed, anyway.
Now, now, that's hardly a fair comparison. Maybe if you grepped for lines
that contain "print" but not "pri
Is it possible with the new parameter declaration syntax to declare
a mandatory name-only parameter?
-Mark
On 2003-08-01 at 09:54:57, Dave Whipp wrote:
> A junction on one element is almost always redundant, and can be cast
> directly into the scalar that is its eigenstate. The only issue with doing
> that is that certain junction methods might not be available. However, in
> the case of a C, an abjunct
On 2003-08-05 at 16:10:46, Dan Sugalski wrote:
> At 1:02 PM -0700 8/5/03, Dave Whipp wrote:
> >Can I discriminate on parameter names using multi subs?
>
> Nope. Named parameters don't participate in MMD.
1. I'm thinking MMD should be called something else when being applied
to multisubs rather
On 2004-12-03 at 14:46:16, John Siracusa wrote:
> Anyway, I thought it was interesting to see the ease of "forward
> compatibility" for simple attributes touted as a feature of Python. I'd
> like to tout it as a feature of Perl 6 too, because I also hate writing
> getters and setters... :)
Amen.
On 2004-12-19 at 21:35:46, Luke Palmer wrote:
>In Perl 5 you can do the hackish:
>
>(\my @foo)->[23] = 42;
Hm. My reaction to the above is, and I think I speak for the entire
assemblage when I say this, "Yuckbo."
:)
Now, (my @foo)[23] would be somewhat better, but of course, that's
On 2005-02-03 at 11:13:30, Autrijus Tang wrote:
>Today I've started implementing typing relations for value types in
>FP6. ...
Shouldn't this have gone to perl6-internals, not perl6-language?
On 2005-02-22 at 14:26:04, Juerd wrote:
>I think \777 should be chr(777). As should \0d777, should you want to
>document that it's really not octal. (Important mostly the first year
>after the first release.)
I don't think you can assume it'll only be confusing for a year. For
one thi
On 2005-02-22 at 15:47:08, Larry Wall wrote:
>Maybe \x is short for \0x and that also gives us \0o, \0d and \0b,
>plus any other radix we come up with, assuming we decide it isn't
>overly ambiguous with bare \0.
Works for me. So when you really do want a \0 in the middle of a string
f
Luke Palmer wrote:
Marcus Adair writes:
> Additionally I question whether this is truly a case improving to the
> point of least surprise? After all, I don't know a programmer who's
> going to be surprised by what true means. There are still *some* things
> you may have to learn in software dev 101
On 2004-04-13 at 13:16:02, David Cantrell wrote:
> Perl 6, we are promised, will try to run "legacy" code unchanged. How
> will it spot such legacy code?
My understanding has been that perl6 will assume a program is Perl 5 unless
it sees a Perl 6 keyword such as 'module' or 'class'.
--
Mark
Scott> * %hash`s is an example of a small thing that would be easy to implement
Scott> in core but would be used constantly (if JavaScript is any indication,
Scott> every few lines), giving a lot of bang for the buck
Not sure that JavaScript is relevant here, since the "equivalent"
syntax there
On 2004-04-15 at 16:49:28, Mark J. Reed wrote:
> Not sure that JavaScript is relevant here, since the "equivalent"
> syntax there, ".", is the same as the method call syntax. But see my
> proposal below.
Before the nit-pickers jump in, I was oversimplifying above.
On 2004-04-15 at 19:39:25, Austin Hastings wrote:
> Of course you used for buffers that were not powers of 2. Had they
> been powers of 2, you would have used & or &~. The fact that you
> didn't use a power of 2 is pretty questionable. The dread Unix
> wizards will no doubt have questions for you
On 2004-04-16 at 00:25:51, Brent 'Dax' Royal-Gordon wrote:
> Number of keystrokes isn't our only concern here. This is Perl, not
> APL--we care about the size of the language and its intuitiveness too.
> (Perhaps not much, but we do.)
In any case, Perl is far more typable than APL unless you ha
On 2004-04-16 at 09:23:44, Mark J. Reed wrote:
> On 2004-04-15 at 19:39:25, Austin Hastings wrote:
> > Of course you used for buffers that were not powers of 2. Had they
> > been powers of 2, you would have used & or &~. The fact that you
> > didn't use a powe
On 2004-04-16 at 11:17:41, Austin Hastings wrote:
> I'm totally willing to agree with you, Mark.
> A) Do you code hashing algorithms so frequently that you need a special,
> low-cost-of-access operator built in to the language to support it?
Nope. I'd be perfectly happy if the modulus operator w
On 2004-04-16 at 08:50:38, Brent 'Dax' Royal-Gordon wrote:
> Mark J. Reed wrote:
> >Nope. I'd be perfectly happy if the modulus operator were spelled "mod"
> >instead of %, which has never struck me as particularly intuitive.
>
> I always saw it a
Let me just chime in with my support for John's basic idea. I would
definitely prefer that it be easy to arrange things such that
$obj.foo = 'bar'
winds up invoking a method on $obj with 'bar' as an argument, rather
than invoking a method on $obj that returns an lvalue to which
'bar' is
On 2004-04-20 at 10:51:47, Luke Palmer wrote:
> I guess I bogged down that message with the implementation, so the
> result may have been easy to miss.
That is what happened in my case. Apologies; it looks like your
original solution would do the job nicely. As long as the requisite
module come
On 2004-04-20 at 11:37:18, Larry Wall wrote:
> So do whatever you like to the declarations, but make sure you preserve
> the symmetry and extensibility of
>
> $obj.foo([EMAIL PROTECTED], *%NONSENSE) # get value of $.foo
> $obj.foo([EMAIL PROTECTED], *%NONSENSE) = 5 # set $
> >>How are those without a US keyboard supposed to type this?
I assume you mean "with" a US keyboard? US keyboards don't have ¥.
You can use " zip " if you want ASCII. Otherwise, it depends. But Yen is
Unicode codepoint U+00A5 = 165 decimal, so you can type it in Windows as ALT +
numpad 0165
On 2004-06-01 at 14:10:08, Paul Seamons wrote:
> Or for the few Perl emacs people out there:
>
> C-x 8 Y
> C-x 8 <
> C-x 8 >
I suspect there are more than a "few". I don't think there's anything
constitutional about folks who like Emacs that prevents them from liking
Perl or vice-versa. Even t
On 2004-06-07 at 21:33:03, David Cantrell wrote:
> This is what is so wrong about allowing unicode operators - yes, I don't
> need to write them, but if some other programmer writes one I have to be
> able to read it. And I can't.
Well, for one thing, just because your email program doesn't let
On 2004-06-14 at 22:58:58, Matthew Walton wrote:
> 'it would be better to explicitly just say
>
> (@list.grep value) = undef
>
> although I think that might be supposed to be
>
> (@list.grep value) »= undef;
Those do different things according to my understanding. The first
removes all matchi
On 2004-07-21 at 09:42:44, Larry Wall wrote:
> Plus it ignores the fact that we've already introduced single character
> scalar context operators that make it trivial to coerce from list
> context to scalar. If {...} supplies list context by default, most
> intepolations are either the same length
On 2004-07-28 at 20:55:28, Piers Cawley wrote:
> What's a math teacher?
Oh, come now. You may refuse to *use* the Leftpondian short form, but
pretending not to *recognize* it is a bit much. :)
--
Mark REED| CNN Internet Technology
1 CNN Center Rm SW0831G | [EMAIL PROTEC
On 2004-08-18 at 22:37:31, Larry Wall wrote:
> Actually, I've settled on .perl for now, on the assumption there could
> also be a .python, a .ruby, a .cobol, a .intercal, etc.
Perhaps there should be a special name visible only at the language
level that automatically translates to .language_I_wa
On 2004-09-14 at 08:40:55, Austin Hastings wrote:
> In particular, I wanted to remove "* but not Makefile" (since my
> Makefile uses lwp-download to re-fetch the source code, etc.)
Well, you can, depending on your shell:
in ksh: rm !(Makefile)
in bash: ditto, but you have to turn on the "extgl
[Recipients trimmed back to just the list, because it had gotten very
silly. When replying to someone who's on the list, there's no need to
copy them personally, too; they just end up with duplicates. :)]
On 2003-09-15 at 09:21:18, Piers Cawley wrote:
> Great. But will it also be possible to add
On 2003-11-25 at 18:17:04, Piers Cawley wrote:
>aString replace: aPattern with: aString.
>
>aString replaceAll: aPattern with: aString.
Stop! Stop that at once! No small talk; we're here for
serious discussions!
:)
> Except... the second argument isn't strictly a string because it's
>
On 2003-11-25 at 19:53:09, Piers Cawley wrote:
> Is that how Ruby does it then?
=begin RubyDigression
Ruby's String class has the methods sub (replace once) and gsub
(replace all), which leave the invocant alone and return the
result of the substitution, and sub! and gsub!, which modify the
invoc
On 2003-11-25 at 13:46:39, John Williams wrote:
> On Mon, 24 Nov 2003, Jonathan Scott Duff wrote:
> > or maybe throw some latin in there
> >
> > while $n++ et @accum < $total { ... }
> > while $n++ cum @accum < $total { ... } # maybe?
>
> I think "ac" is the latin conjunction you
On 2003-11-26 at 12:13:39, chromatic wrote:
> Consider Perl 5, where File::Find is a core module. While the interface
> may have been nice in 1995 (though I doubt even that), it's been widely
> regarded as awful for at least three years. It's likely never to be
> removed from the core. File::Fin
On 2003-12-10 at 15:05:09, The Perl 6 Summarizer wrote:
> Oh yes, if you've not been following, "^op" (ie, the vector operators)
> has become " >>op<< " which is, if nothing else, a right swine to write
> in a POD C<> escape.
Eh, >>op<< is just a hack for people who can't type C<»op«>
chromatic> With Apocalypse 12 (soon!)
RobinBerjon> how soon? :)
LarryWall> here's the rough outline
[indicating that it's pretty soon indeed]
Cool! But now I'm a little confused - what happened to Apocalypses 8
through 11? :)
-Mark
Should Perl6::Slurp be added to Bundle::Perl6? Or is that not being kept
up-to-date?
--
Mark REED| CNN Internet Technology
1 CNN Center Rm SW0831G | [EMAIL PROTECTED]
Atlanta, GA 30348 USA | +1 404 827 4754
On 2004-03-13 at 09:02:50, Karl Brodowsky wrote:
> For these guys Unicode is not so attractive, because it kind of doubles the
> size of their files,
Unicode per se doesn't do anything to file sizes; it's all in how you
encode it. The UTF-8 encoding is not so attractive in locales that make
heav
On 2004-03-16 at 00:28:32, Karl Brodowsky wrote:
> Mark J. Reed wrote:
>
> >Unicode per se doesn't do anything to file sizes; it's all in how you
> >encode it.
>
> Yes. And basically there are common ways to encode this: utf-8 and utf-16
> (or similar varian
On 2004-03-20 at 22:32:18, Calle Dybedahl wrote:
> You don't need Unicode display « and », just plain old ISO 8859-1.
> They're characters number 171 and 187 there. And AFAIK every Emacs
> version released in the past ten years handles ISO-8859-1 out of the
> box. It's more likely that you're usin
Juerd: your message arrived in my inbox as an attachment due to a mail server
along the way not recognizing the "charset" value. It should be "utf-8"
with the hyphen, not "utf8". Also for that reason all the non-ASCII
characters (like the Yen symbol) came through as '?' here.
> Kara Perlistoj,
On 2004-03-26 at 08:16:07, Larry Wall wrote:
> And "say" isn't in there because of APL or PHP. It's actually inspired
> by something worse in Ruby.
Presumably by "something worse" you mean "puts"? Not a great name, to
be sure, but it does have a venerable tradition behind it. :)
I do like ha
@ary[0,0] = list(foo());
--
Mark J. REED<[EMAIL PROTECTED]>
inserted into the
loop block's lexical scope, even though it's declared outside of
the latter's curlies)? If so, I must have missed a mind-change in
that thread; if not, then putting the 'my' inside the parens is a
tad misleading . . .
--
Mark J. REED<[EMAIL PROTECTED]>
which is the result of step 5.
This is where my interpretation fails because the result of step 5
is not an lvalue.
Then again, it's probably using some syntax that I haven't internalized
yet.
--
Mark J. REED<[EMAIL PROTECTED]>
and-line switch to turn on Perl6 mode.
Darn that backwards compatibility, anyway . . .
--
Mark J. REED<[EMAIL PROTECTED]>
>.m2; # syntax error
Doesn't that violate your stated rule that"the default topic within a
method be the invocant? Shouldn't .m2 be equivalent to $_.m2?
--
Mark J. REED<[EMAIL PROTECTED]>
ng with that; I'm just not aware of
that decision having been made. I guess we won't find out for sure
until either Apoc6 or Apoc12?
--
Mark J. REED<[EMAIL PROTECTED]>
m2 within m1's class, regardless of how m1 was called
m2() # call subroutine m2 with no arguments, implied or otherwise
--
Mark J. REED<[EMAIL PROTECTED]>
On Wed, Apr 10, 2002 at 03:03:45PM -0400, Mark J. Reed wrote:
> ..class.m2: # call static m2 within m1's class, regardless of how m1 was called
Typo. That should be just .class.m2, only one leading '.'.
--
Mark J. REED<[EMAIL PROTECTED]>
On Wed, Apr 10, 2002 at 12:12:56PM -0700, David Whipp wrote:
> Mark J. Reed wrote
> > On Wed, Apr 10, 2002 at 03:03:45PM -0400, Mark J. Reed wrote:
> > > ..class.m2: # call static m2 within m1's class, regardless
> > of how m1 was called
> > Typo. That should
t's not getting
stripped off properly. That was supposed to be a single '.' in front of
the m2(). In other words, unary . is the same as binary . with $_ as
the LHS, so .m2() would be the same as $_.m2(). Which would have the
semantics in my comment above, assuming that the class becomes the topic
in static methods.
--
Mark J. REED<[EMAIL PROTECTED]>
On Wed, May 01, 2002 at 12:11:58PM -0700, Brent Dax wrote:
> It's far too late to make it into 5.8, but it looks like it'll be in
> 5.10 when that comes out (in a year or two).
.. . . by which time 6.0 will have already been released, right?
Right?
--
Mark J. REED<[EMAIL PROTECTED]>
On Sun, May 12, 2002 at 12:30:20AM +0200, Pixel wrote:
> FYI Ruby has:
>
> a.type <= b.type or a.type == b.type
>
> where the various operators (<, >, ==, != ...) are overloaded
> according to the subtyping relation.
>
> as for me,
> - i find the "==" very readable,
> - but i'm not sure "<=
re stat, but maybe this answer is a good
end-of-chapter sorta thing.
I'll also have to think about using given {} merely as a topicalizer
too, I guess, although showing it next to an explicit assignment to $_.
:)
--
Mark J. Reed <[EMAIL PROTECTED]>
ing global variables initialized to named
constants, e.g. $stderr starts out as equal to STDERR but can be
reassigned...
--
Mark J. Reed <[EMAIL PROTECTED]>
*DEFERR would be kinder to embedding
systems that want to intercept such messages and log them.
Right. Something akin to P5's $SIG{__WARN__} and $SIG{__DIE__} would
also work, but that never seemed to be quite the right way to do that,
to me.
--
Mark J. Reed <[EMAIL PROTECTED]>
is a method on
the filehandle object, but called what? Should it keep the P5
IO::Handle name (input_line_number)? Or something else perhaps a
little less unwieldy (lineno, recno, ...)
I don't see any reference to $. in the Synopses, so I assume this is
not yet defined. Apologies if I just
t's
still pretty rudimentary.
Ah, thanks! Missed that.
As for $. itself as a variable, it's dead.
Yeah, kinda figured.
there are very, very few punctuational variables in Perl 6 compared to Perl 5.
Most of
'em are just gone.
And a cheer went up from the multitude... :)
Thanks again for the reply.
--
Mark J. Reed <[EMAIL PROTECTED]>
not steal them?
BTW: Why do so much people say "go away if you don't like it" instead of
being open for ideas and discussing them from a neutral point of view?
--
Thomas Wittek
http://gedankenkonstrukt.de/
Jabber: [EMAIL PROTECTED]
--
Mark J. Reed <[EMAIL PROTECTED]>
s the hash to have a single
element whose key is the hash reference provided and whose value is
undef... but in P6 that does the right thing.)
--
Mark J. Reed <[EMAIL PROTECTED]>
', 'a');
I don't know why I think that makes sense, but it was honestly my
first thought. Does it make sense to anyone else? Is there a
compelling reason I'm missing for having negative values behave as if
they were zero rather than adding some other potentially useful
functionality?
--
Mark J. Reed <[EMAIL PROTECTED]>
odded to see what was going on in @larry.brain. Your
explanation is all I needed to shush the little grumbles in my head.
Thanks again!
--
Mark J. Reed <[EMAIL PROTECTED]>
ing namespace
+Any Perl 6 object (default parameter type, excludes Junction)
+Object Perl 6 object (either Any or Junction)
A C differs from a normal C in how it handles default
values. If the value of a C element is set to the default
--
Mark J. Reed <[EMAIL PROTECTED]>
of candidates:
Indeed. Something shorter might be nice, but I wasn't proposing a
rename. Besides, "Top" just reeks of LDAP. Oh, and you left out
"Root". It being the root of the type hierarchy and all.
Life::Universe::Everything
...which no doubt numifies to 42.
Thanks again for answering my silly questions.
--
Mark J. Reed <[EMAIL PROTECTED]>
English" pragma? :)
Are you the one who originally came up with "hash" for %vars? IIRC,
they were officially called just "associative arrays" through Perl4,
but "hash" was a well-understood community nickname for them for some
time before you canonized it wi
nce a random
rearrangement of the inputs. Hence, a hash.
--
Mark J. Reed <[EMAIL PROTECTED]>
French "hache", but you have to go back to Norman times to get there.
The word "hash" has been an English word for almost a millennium, and
"hashed browns" are simply browns (browned potatoes) that have been
hashed...
--
Mark J. Reed <[EMAIL PROTECTED]>
ot;~cat($n xx *)" might work.
Personally, I would tend to favor the notion that infix: always
produces a single string. With this in mind, I'm now leaning toward
"~cat($a xx $n)" as the more verbose equivalent of "$a x $n". You
always produce a single string, and you do so lazily (according to the
way that 'cat' works in item context).
--
Jonathan "Dataweaver" Lang
--
Mark J. Reed <[EMAIL PROTECTED]>
.
> > That's understandable at the moment since cc_build doesn't seem to have
a
> > documented return value. It should, of course.
I agree with chromatic -- I'd simply add that the cc_build() function
should be improved to have a meaningful return value, not that it should
be avoided.
--
Andy Dougherty [EMAIL PROTECTED]
--
Mark J. Reed <[EMAIL PROTECTED]>
s.
"""
this needs implementation.
Is a system() call legit at that point of the config? Because I can
think of no reliable, general way of looking for fink other than
trying to run the fink command...
--
Mark J. Reed <[EMAIL PROTECTED]>
s
> > to true or false.
>
> Can we *please* keep simple things simple?
Agreed. I'm in favor of this proposal to the extent that it breaks a
simple trinary operator down into equally simple binary operators
(with the trinary form continuing to exist as an emergent property of
the interaction of the binaries); if those binary operators become
more complex than the trinary form, or if you lose the ability to
recover the trinary form from them, there's no point in pursuing this
proposal.
--
Jonathan "Dataweaver" Lang
--
Mark J. Reed <[EMAIL PROTECTED]>
. Sure, x might be a pointer, and
things might gang agley there, but pointers getting set to the wrong
type of pointee is a pretty common problem, and one that I'm happy to
have some runtime support in locating.
--
Mark J. Reed <[EMAIL PROTECTED]>
since the compiler will automatically complain if the two pointers
don't point to the same type of object. AFAICT, the wrapping around
the assignment in the macro just makes sure that there aren't any side
effects - but the only reason side effects would be a problem is that
it's a
On 6/21/07, Andy Lester <[EMAIL PROTECTED]> wrote:
We now have STRUCT_COPY(dest,src) and STRUCT_COPY_N(dest,src,n) for
all your struct-copying needs.
Wait! Wait! It should be src, THEN dest!
--
Mark J. Reed <[EMAIL PROTECTED]>
On 6/21/07, Joshua Isom <[EMAIL PROTECTED]> wrote:
> Wait! Wait! It should be src, THEN dest!
Are you an AT&T guy or an Intel guy?
Neither! 68k assembly FTW!
--
Mark J. Reed <[EMAIL PROTECTED]>
adverbial colon needs whitespace before but not after?
>
> The reason I ask is that I'm knocking up an intro to Perl 6 for C and C++
> programmers. I expect some of Perl 6's whitespace rules to trip up people
> used to C++ (as they have me, in my clumsy attempts with Pugs), and I'd
> like to summarise all the whitespace dwimmery in one place.
>
> Many thanks,
>
> Markus
>
--
Mark J. Reed <[EMAIL PROTECTED]>
On Nov 29, 2007 10:07 AM, James Fuller <[EMAIL PROTECTED]> wrote:
> Once again, the point is that I would like to manage and process XML
> using native types, structures and xml aware operators, from within
> perl. If I inherit XPATH, then I get 90% of everything I need.
But what do you mean "nat
nted out, this sort of discussion belongs somewhere else.
> Note that no language really shines on the web: it's something that
> someone makes with the language (e.g. Catalyst, Rails, Seaside, Django)
> that shines on the web :)
>
--
Mark J. Reed <[EMAIL PROTECTED]>
idioms, words a good idea?
> There're bunch of words that could describe the same idea
> in a sligtly different manner.
> Perhaps writting a la smallTalk could be the solution.
> getting rid off all shortcuts and change them into explicit description
> entities and write english sentences, not programs.
> This could be nice but I will first have to learn English.
> Anyway, I will write my own 'Lingua::Given::Francais' with avec ...
> lorsque^^:
> (well, if I can - ^^; xx 1000 )
>
>
>
> --
> シリル・デュモン（Cyrille Dumont）
> [EMAIL PROTECTED]
> our work is the portrait of ourselves
> tel: 03-5690-0230 fax: 03-5690-7366
> http://www.comquest.co.jp
>
>
>
--
Mark J. Reed <[EMAIL PROTECTED]>
braces (which is consistent to how they are used in other
> expressions of the language).
>
> It is all there somewhere in Section "Literals" of Synopsis 02
> (http://perlcabal.org/syn/S02.html#Literals). More specifically, look
> for the item that starts with "In addition to q and qq, there is now
> the base form Q".
>
> Kind regards,
> Adriano Ferreira
>
> > --
> > ...they shared one last kiss that left a bitter yet sweet taste in her
> > mouth--kind of like throwing up after eating a junior mint.
> > -- Dishonorable Mention, 2005 Bulwer-Lytton Fiction Contest
> >by Tami Farmer
> >
> >
>
--
Mark J. Reed <[EMAIL PROTECTED]>
101 - 200 of 516 matches
Mail list logo
