rk as an assertation, instead of having this
strange "as if" thing?
-=- James Mastros,
theorbtwo
p calling out to the smartmatcher.
Possibly we should make the syntax be a smart match, but only require that
conformat implementations implement ranges and integers.
-=- James Mastros
uot;environment variable" is something
in %*ENV. An "environmental variable" is a variable which was declared with
env $foo, and which can be seen by callers.
I rather dislike this naming scheme, but can't think of a better one.
-=- James Mastros
3 legal perl6? my ($foo, undef, $bar) =
1..3; is valid perl5, but AFAIK that is completely undocumented. (It's
quite useful from time to time -- now if only my (@rest, $almost, $last) =
function_returning_many_thingies could work...
-=- James Mastros
be terribly common such that the extra cognative
overhead is worth it, come to think of it.
I withdraw the (stupid) suggestion.
-=- James Mastros
ften.
Also, as a checklist for proposals. If you're thinking of proposing
something, go look there. If it's already there, do you have any new pros
to put against the existing cons?
-=- James Mastros
(This assumes that the float synthax will be extended to include "NaN" and
"Inf" as valid
floating-point numbers. (This does take away from non-reserved namespace.)
Has this
been proposed yet?)
-=- James Mastros,
In slightly over his head.
ive)infinite value means
that it becomes non-infinite, IE scalar((-inf..0)) != inf. This is
obviously a Bad Thing. Also, if bignums are intergrated (as has been
proposed), then there is no smallest representable integer.
-=- James Mastros,
In slightly over his head.
quot; attribute, and then
assigns 42 to it.
OTOH, the constant attribute is set after the assignment -- otherwise the
assignment would
always be in error!
-=- James Mastros
DWR could still be defined as a sub that always returns a constant.
That being said, I like the $O{RDWR} suggestion... It's just irrelevent to
the
point of this RFC.
-=- James Mastros
that takes a BLOCK), and label is the label of
the loop, or name of the sub (if non-anonymous).
What do you guys think?
-=- James Mastros
. We need syntax that allows something like:
>
> my int @sparse_array : sparse(0,0.99) = ((0) x 5 , 1);
Ahh, it does. See the attributes module. You're example would have to be
somthing like "my int @sparse_array : sparse((0,0.99) = ((0) x 50_000, 1));"
as the attribute's arguments have to be in a parenthesized phrase.
-=- James Mastros
eant by the default filehandle in the New Perl Order. (It's in the
air at present whether the puncuation varables will continue as a way to set
stuff for all filehandles that havn't had stuff explicitly set for them, if
there will be some other method for that, or if doing that won't
work" without any further ado. Note also that this
means that :no_lvalue can be written in pure perl.
-=- James Mastros
always increase speed, but
won't allow as much expressiveness.
-=- James Mastros
--
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GU>CS d->-- s-:- a20 C++ UL+++@ P+++>+ L++@ E-() N o? K? w@ M-- !V
PS++ PE Y+ PGP(-) t++@ 5+ X+++ R+ tv+ b+++ DI+ D+ G e>++ h! r- y?
--END GEEK CODE BLOCK--
On Sat, Aug 19, 2000 at 07:57:34AM +1000, Jeremy Howard wrote:
> The choice of algorithms is a great idea, but why do we need a modifier?
> Isn't it a pretty straightforward set of rules that allow us to decide if a
> DFA matcher will work?
Well, that all depends what the meaning of the word work
dity is self-evident, or so nice an idea that
it's goodness is self-evident.
-=- James Mastros
proposed meaning of want wouldn't allow you to do
that, or the way I read this, even modify the value of existing keys. While
this hardly makes it useless, it doesn't make it nearly as useful as it
could/should be.
Making the CODE(ref/HOF) parameter get aliases rather then values helps a
little, but not enough -- you still couldn't create new keys in the hash.
-=- James Mastros
27;s being
called at compiletime or runtime.
Please CC me on any replies; I'm probably going to unsubscribe from
perl6-language-*.
-=- James Mastros
From: "Nathan Wiger" <[EMAIL PROTECTED]>
To: "James Mastros" <[EMAIL PROTECTED]>
Sent: Thursday, September 14, 2000 5:32 PM
Subject: Re: RFCs up for adoption, and a proto-RFC
> James Mastros wrote:
> > RFC 163: Automatic accessors for hash-based obj
ly get
the location of the AUTOLOADER sub and not where the sub being autoloaded
was acatualy written.
Most of the rest would require siginificant overhead on all programs that
might get debugged (the debugger is a module; you don't necessarly have to
start it from the commandline). Us
can run freely in the end-user's account. Think
cgi_wrapper without spawning a new interpreter.
-=- James Mastros
--
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GU>CS d->-- s-:- a20 C++ UL+++@ P+++>+ L++@ E-() N o? K? w@ M-- !V
PS++ PE Y+ PGP(-) t++@ 5+ X+++ R+ tv+ b+++ DI+ D+ G e>++ h! r- y?
--END GEEK CODE BLOCK--
From: "Adam Turoff" <[EMAIL PROTECTED]>
> On Wed, Sep 27, 2000 at 12:09:20PM -0400, James Mastros wrote:
> > Really, I don't see why we can't
> > just have a 'use taint' and 'no taint' pargma.
>
> Because taint mode needs to
strict
"taint"'. (in default strict set?)
Hm, this behavor would be equivlent to making "unsafe" errors normal:
'no strict "taint"' == 'no taint'
'use strict "taint"' == 'use taint'
'use warnings "taint"' == 'use taint warnings'
(You'd have to put the warnings/errors about 'no taint' in the 'notaint'
set.)
-=- James Mastros
the value of
$hash{elem}, not on the spot in the hash.
I don't know what a good syntax for the hash position would be. And I've
got other work to do now.
-=- James Mastros
Creating attributes:
--
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GU>CS d->-- s-:- a20
From: "Nathan Wiger" <[EMAIL PROTECTED]>
Sent: Friday, September 29, 2000 12:51 AM
> James Mastros wrote:
> > As far as setting|getting, I'd like to make a simple proposal. Consider
it
> > an idea for whoever writes the RFC (I'm looking at you, Nat
ns. I
personaly would prefer to see units of seconds, a basepoint of 1/1/1970, and
resolution and accuracy best-reasonably-available.)
If you really want time() to do what it did before, you can always say:
sub time {int (CORE::time()) + };
Indeed, a perl5::time module that does exactly that mi
change the meaning of time() slightly without changing to a
different function name? Yes, it will silently break some existing code,
but that's OK -- remember, 90% with traslation, 75% without. being in that
middle 15% isn't a bad thing.
-=- James Mastros
--
"My country
s result slightly differently is not "not
keeping perl perl", nor is it not keeping time time; changing time() such
that it did somthing radicly different (like returning time-of-day instead)
would be changing it's soul.
And I don't think we should be keeping code-level compatablit
't modify it. And if you try, you don't error, you
recruse. And perl will happily recruse until you run out of memory, and VB
will give a stack overflow, and take down the IDE and your code unless
you're careful.
-=- James Mastros
--
"My country 'tis of thee, of y
AC address of
the network card, and some other random stuff).
I think the current method is probably best for us.
-=- James Mastros
--
"My country 'tis of thee, of y'all i'm rappin'! Lan where my brothers
fought, land where our King was shot -- from every buildi
#x27;s SysV IPC scheme into perl. (And I
don't even know what XPG4 is.)
Speaking of contract names, is Damien about?
-=- James Mastros
--
"My country 'tis of thee, of y'all i'm rappin'! Lan where my brothers
fought, land where our King was shot -- from eve
contain two
consecutive colons. (or "'"s, but that's going to be thrown out, I assume).
-=- James Mastros
--
"My country 'tis of thee, of y'all i'm rappin'! Lan where my brothers
fought, land where our King was shot -- from every building
On Fri, Feb 02, 2001 at 05:01:29PM -0600, David L. Nicol wrote:
> > A /much/ better syntax, in [John Mastros's] humble opinion. However,
"James", BTW. (No, I don't really care.)
> > $__ must act sanely when we're called as an inner function (IE foo(bar(42)
On Sun, Feb 04, 2001 at 05:30:59PM +0100, Johan Vromans wrote:
> James Mastros <[EMAIL PROTECTED]> writes:
> > And I always hated that about VB and Pascal -- you can assign to the magic
> > variable, but can't modify it.
>
> That was before the invention of a
ffer is two magic values, $^R and @^R. And, as
sombodyoranother pointed out, @^R can't be a real array, only a list. (I
don't think that will be a problem, though.)
> [stuff about manual vs. automatic return-stack elminition]
Yeah, you're probably right. But return-as-assignment
it's independent of the sub's name. I wish this could be
> extended to doing recursive calls without having to say the subs own
> name, again.
I agree, making the magic variable be the name of the sub is a bad idea.
Your idea for a name for the currently executing sub is interesting, I
thin
ormation
on scopes that caller doesn't (IE any scope not a do, require, eval, or
sub-call.)
-=- James Mastros
--
"My country 'tis of thee, of y'all i'm rappin'! Lan where my brothers
fought, land where our King was shot -- from every building top, le
On Mon, Feb 05, 2001 at 08:43:02PM +0100, [EMAIL PROTECTED] wrote:
> On Mon, Feb 05, 2001 at 11:46:48AM -0500, James Mastros wrote:
> > By the time you get to the last line, you've already forgoten WTF you named
> > the return variable.
> Eh, I don't think that b
No | Yes |
No. (Source packages are signed, though.) (At present, feature is planned
for future, and shouldn't be all that hard.)
-=- James Mastros
--
"All I really want is somebody to curl up with and pretend the world is a
safe place."
AIM: theorbtwo homepage: http://www.rtweb.net/theorb/
sumers, assumedly)
licenced code from RSA. However, it shouldn't be a problem, since RSA's
pattent (in the US, anyway, and I don't think they pattented anywhere else)
has timed out.
-=- James Mastros
--
"All I really want is somebody to curl up with and pretend the world
them that knows how to do special things with
files in that directory (like set up symlinks from the normal man dirs).
BTW, this plan would make it painful to do with perl5 setups, since they
commonly have odd dir structures.
-=- James Mastros
--
"All I really want is somebody to cur
On Mon, Feb 12, 2001 at 06:56:47PM -0300, Branden wrote:
> James Mastros wrote:
> > magical "install" script in them that knows how to do special things with
> > files in that directory (like set up symlinks from the normal man dirs).
>
> That probably should be
(cond) { somthing } }.
CATCH is just shorthand.
> - What's the return value? With RFC 88 you can say:
The return value is undef (or empty-list) until you hit a return statement.
If the code dies before returning, then it stays undef/() unless somthing
run after that (IE a CATCH/POS
uctor)
Fiat?
It's pretty hard (for me) to think of when you'd want an AUTOLOADed DESTROY,
since if you create /any/ objects of the class, DESTROY will be called.
"It isn't possible to AUTOLOAD DESTROY." --perlmem(6)
-=- James Mastros
--
"All I really want is so
On Tue, Feb 13, 2001 at 01:09:11PM -0500, John Porter wrote:
> > James Mastros wrote:
> > >"It isn't possible to AUTOLOAD DESTROY." --perlmem(6)
[Note: that's a hypothetical quote.]
> I'm not sure what that means. Certainly AUTOLOAD gets
> called
with a message about ``This object was already
> DESTROYed.''.
I think an ordinary "attempt to dereference undef" will work.
-=- James Mastros
--
"All I really want is somebody to curl up with and pretend the world is a
safe place."
AIM: theorbtwo homepage: http://www.rtweb.net/theorb/
On Wed, Feb 14, 2001 at 09:59:31AM -0500, John Porter wrote:
> James Mastros wrote:
> > I'd think that an extension to delete is in order here. Basicly, delete
> > should DESTROY the arg, change it's value to undef,...
> Huh? What delete are you thinking of? This is
tly GC.
3) Automatic -- Certian runtime events, not directly (or obviously) related
to the flow of execution, like when the number of SVs created or the
amount of memory allocated since the last GC run exced a certian critical
value.
(I /think/ a dictionary would agree with me, but I'm not about to get pissy
and look them up.)
I was saying that we should do 1 and 3, but not 2.
-=- James Mastros
hat there would be a "invalid" marker of some sort.
It's neccessary (I think) for a pool, which I assumed. Bad James, bad.
-=- James Mastros
--
"All I really want is somebody to curl up with and pretend the world is a
safe place."
AIM: theorbtwo homepage: http://www.rtweb.net/theorb/
t; is immediate).
I'm fond of post, myself. Simply means "subsequent to", literaly (m-w.com,
post-, 2a. Yes, I'm anal sometimes.) "Always" makes me say "but when", and
"later" seems like the wrong part-of-speech to me.
-=- James Mastros
--
t;sub {}"s.)
Indeed,
map $_->[0], sort {&$sort($a->[1], $b->[1])} map [$_, &$attrib($_)], @list;
does what I intendeded. (Where ex $sort = sub {$_[0] cmp $_[1]}, and
$attrib = sub {lc $_}.) (Of course, this doesn't always use the optimal
form.)
-=- James Mastr
] elem, and extract the ->[1] elem. Thus, it might not be as
effecent as a hand-crafted schwartzian, but will be at least as efficent as
a naieve straight sort (except in pathalogical cases, like tsort((^_),
(^_<=>^_), @list)).
-=- James Mastros
--
The most beautiful thing we c
g out of his head
> and hiding behind the bookcase)
That's a really wierd image. Twisted, even.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true art and science. He to whom this emotion is a stranger,
who can no longer pa
Then again, if you think of objects (in the OO sense) as doing things, then
they normaly are the subject, and _not_ the indirect-object (in the english
sense).
(Note, BTW, that both my german and my lingustics aren't so hot.)
-=- James Mastros
--
The most beautiful thing we can experi
n
indicator that you should be using that schwartz thang.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true art and science. He to whom this emotion is a stranger,
who can no longer pause to wonder and stand wrapt in awe, is as
On Mon, Mar 26, 2001 at 06:31:22PM -0500, Dan Sugalski wrote:
> At 04:04 PM 3/26/2001 -0500, James Mastros wrote:
> >The only way f(a) can not be stable and f(a) <=> f(b) can be is somthing of
> >a corner case. In fact, it's a lot of a corner case.
> You're ig
")=123456
f(f("+123,456))=123456
The functon is not idempotent. Even if you checked f(x)==x (function is the
identity), an input of "123456" would work.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true
>my_compare(b,c) < 0, then it should also be the case that
> >my_compare(a,c) < 0
I can't define it better then that. (Though there's more to it then that).
Note that only the sign of the answer is gaurnteed, so it doesn't even have
to be interna
that increment a
counter every time they are accessed, for example.)
I think that the difference between 4&3 dosn't matter. We only have things
in 4 and not 3 that vary in abs(), but not sign.
We're left with 1&2, and for 1, the sort won't work anyway.
So long as we consid
te such as
:simple or :stateless. So let it be spoken, so let it be done.
This isn't any more preverse then the "you can't assign to constants" rule.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true art and
On Wed, Mar 28, 2001 at 05:57:30PM -0500, James Mastros wrote:
> [A bunch of stuff]
Oh, and I agree with sombody else on this thread that unless otherwise
stated, the sort should always assume statelessness (and thus the ability to
cache at will). If it's trivial to see that the sort
dvanced garbage collector, just like
> Scheme or Strongtalk compiler?
We want to make it as fast as reasonably possible. Writing a native
compiler might not be _reasonably_ possible. And an advanced GC will almost
certianly be part of perl6; they're orthogonal issues.
-=-
o english as a command
form, telling the Cow to speak. (If you translate both -> and ' ' into a
comma.)
Anyway, I'm trying to argue lingustics in a perl ML, with zero training.
Is there a linguist in the house? (Hm, didn't Larry go to Japan to learn a
language with wierd
arison for the same
> arguments.
Ahh, bingo. That's what a number of people (inculding me) are suggesting --
a :functional / :pure / :stateless / :somthingelseIdontrecall attribute
attachable to a sub.
-=- James Mastros
--
The most beautiful thing we can experience is the myster
a better system, use
a site-policy file, or bite the bullet and change the #! lines.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true art and science. He to whom this emotion is a stranger,
who can no longer pause to wond
't symlink
bunzip -> bunzip2 and bzip -> bzip2 and have it do the Right Thing. On the
gripping hand, when combined with other mesures, not so bad.
-=- James Mastros
--
The most beautiful thing we can experience is the mysterious. It is the
source of all true art and science. H
you
really want to be able to read from a URL in one line, let yourself do
. But make opening a URL an explicit act.
> But I really mustn't spill too many half-digested beans here. :-)
If you have to, at least do it in the toilet.
> P.S. Larry's Second Law of Language Rede
ewhere on these threads: What does changing to "." from -> buy us?
I can see that "." is shorter to type then ->, but, say, \ would be just as
good. I can't really say changing because "." is more standard. It isn't
standard to C or perl5. It's possible to misparse "." as concat with "." as
a sepperator on version-strings, but that's more of a problem with using it
for method-call.
-=- James Mastros
If you want that, you could go with `, which could produce some
ambiguity, both with qx and with ', which looks very similar in many fonts.
BTW, I think that considering no-whitespace cases of indirect object is
quite silly -- does anybody acatualy use that?
This is the first I thought it wasn't a syntax error.
-=- James Mastros
9 !097!0!9080"; would
stop looking after it had found and returned 0!0 and 9, and never even
glance at the 98. Basicly, if you assign to a list of lvalues, @returnlist,
it
will stop looking after it has found scalar(@returnlist) matches or
end-of-input.
-=- James Mastros
and I think the use of := agrees with what is planned.
It also avoids the use of a verbose .next (and the dot, which I still don't
like ).
-=- James Mastros
ive), so I'd rather we stay with:
>$a = <$b>; # same as next $b or $b.next
> Hey, maybe we can convince Larry... ;-)
I'd tend to agree. Especialy that we don't need a qw() alternative.
However, I don't think Larry's in a convincable mood -- coughdotcough.
-=- James Mastros
).
That lets us keep for somthing iteratorish, which saves
special-caseing (I do occasionaly use a qw list with one element),
and lets us keep continuity.
Anyway, I'm fairly certian that I'll use iterators more then qw lists.
-=- James Mastros
ers) within one file, and having perl5 being another parser. Put them
together, and you get exactly this.
-=- James Mastros
infix .new.
>
> (args)`Class;
The problem with it is that somehow we have to get 5`m / 30`s to work,
even though m is an operator, which AFAIK means it needs to be a macro,
or the moral equivalent (is parsed).
Also, having every unit be a like-named class would very muc
ements, but
it compares as a range. 1.1 should ~~ 1..2; pugs thinking that's false is a
bug, not a feature.
Of course, that doesn't mean implementing range in a subset of perl6 without
it isn't interesting, and possibly useful for bootstrapping.
-=- James Mastros
name than 'regex'.
[...]
> Maybe 'match' is a better keyword.
Can I suggest we keep match meaning thing you get when you run a thingy
against a string, and make "matcher" be the thingy that gets run?
100% agree with you, Allison; thanks for putting words to "doesn't feel
right".
-=- James Mastros
ould have a s/z/s/ version, for
those who speak a z-impared dialect of English.)
-=- James Mastros
there seems to be a dearth of xml 'ness' in Perl 6 design ... perhaps
before Perl 6 is fully baked its time to review what could live in the
core versus an external module.
thoughts?
cheers, Jim Fuller
ence processing deep into perl6.
making perl 6 XML-neutral is a mistake. imho.
cheers, Jim Fuller
On Nov 28, 2007 7:12 PM, Nicholas Clark <[EMAIL PROTECTED]> wrote:
>
> On Wed, Nov 28, 2007 at 06:06:14PM +0100, James Fuller wrote:
> > there seems to be a dearth of xml 'ne
On Nov 28, 2007 7:31 PM, C.J. Adams-Collier <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-11-28 at 18:12 +, Nicholas Clark wrote:
> > On Wed, Nov 28, 2007 at 06:06:14PM +0100, James Fuller wrote:
> > > there seems to be a dearth of xml 'ness' in Perl 6 design
On Nov 28, 2007 7:39 PM, Andy Armstrong <[EMAIL PROTECTED]> wrote:
> On 28 Nov 2007, at 18:28, James Fuller wrote:
>
> > A few things I could imagine; native XML data type (and whatever that
> > means at this late stage)
>
> What might that mean at any stage?
On Nov 28, 2007 7:50 PM, Geoffrey Broadwell <[EMAIL PROTECTED]> wrote:
> Not too put too strong a bias on it, but:
>
> XML processors are a dime a dozen. There is no way for us to know *now*
> what the "best" XML processor(s) will be a decade from now, and Perl 6
> is intended to be a very long te
On Nov 28, 2007 8:46 PM, chromatic <[EMAIL PROTECTED]> wrote:
> On Wednesday 28 November 2007 10:59:30 James Fuller wrote:
>
> > I do not nec. agree with 'a particular grammer is not' part of the
> > core ... if that grammar is so common to every problem (like reg
On Nov 29, 2007 7:45 AM, Alex Kapranoff <[EMAIL PROTECTED]> wrote:
> В Чтв, 29/11/2007 в 07:18 +0100, James Fuller пишет:
> > On Nov 28, 2007 8:46 PM, chromatic <[EMAIL PROTECTED]> wrote:
> > > On Wednesday 28 November 2007 10:59:30 James Fuller wrote:
>
On Nov 28, 2007 8:48 PM, Geoffrey Broadwell <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-11-28 at 19:59 +0100, James Fuller wrote:
> > XML Parser is what I am talking about
>
> OK -- do you want an event-based parser? Do you want a DOM parser? Do
> you want a simplified tr
On Nov 29, 2007 12:01 PM, Smylers <[EMAIL PROTECTED]> wrote:
> So, to make a claim for any 'domain-specific' functionality to be added
there are plenty of core perl functions that you or I will use rarely
(both in perl 5 and perl 6).
my claim is that XML is significantly common place, that any ne
On Nov 29, 2007 1:15 PM, Luke Palmer <[EMAIL PROTECTED]> wrote:
> This has become quite the flame war. There seem to be two sides of
> the argument, you arguing one, everybody else arguing the other.
good to see there is passion underlying perl 6 development ;)
> So to bring some perspective bac
On Nov 29, 2007 1:15 PM, Luke Palmer <[EMAIL PROTECTED]> wrote:
> language? What would you be able to do with it that you couldn't do
> if it were a module
> (arguments such as "use it without putting 'use XML::Foo' at the top"
> considered valid)?
and to answer specifically the question;
'What
On Nov 29, 2007 3:44 PM, Smylers <[EMAIL PROTECTED]> wrote:
> What makes you so sure that nobody will come up with a better way of
> working with XML
there is power in everyone doing the same thing ... this is a
variation of lingua franca design pattern.
For example, would we say that the reason
Thanks to all for taking the time to respond at a minimum the
discussion has taught me where perl 6 is headed and where the major
architectural brake points currently are.
gl, Jim Fuller
can I add a few unsolicited ruminations from a lurker;
* just release perl 6 now and move on
* do not hire 40 year olds with responsibilities, convince the
young to spend their time for free ... isn't that what one is supposed
to do after the age of 40 ?
* use all funds to promote its u
On Wed, Mar 26, 2008 at 7:44 PM, Richard Dice <[EMAIL PROTECTED]> wrote:
> What all of myself, chromatic and Richard Hainsworth seem to appreciate is
> that a plan without resources to back it up is almost guaranteed to be
> ineffective. Even more than that, we have an appreciation that planning
nice work,
I think this kind of redrafting can be a good foundation for
refactoring ... though I would go further and suggest an xml based
format ... if u have a .odt you can convert this to docbook ;)
one nit pick; drop 'rigorous' in title
Jim Fuller
On Wed, Apr 30, 2008 at 9:14 PM, Jon Lang <[EMAIL PROTECTED]> wrote:
> Brandon S. Allbery KF8NH wrote:
>
> > TSa wrote:
> > > I totally agree! Using 'isa' pulls in the type checker. Do we have the
> > > same option for 'does' e.g. 'doesa'? Or is type checking always implied
> > > in role composi
I think if the logo alluded to something revolving around a xmas
present would be appropriate.
-Jim Fuller
creating a logo by committee is probably the worst way to design such
things ... perl6 logo will be seen in the context of other more
professionally designed logos and like it or not using the basics of
modern branding and marketing will result in something that is more
recognizable no matter
udience: robust, trusted, straightforward, safe, supported
colors evoke meaning, shapes/animals, etc do as well ...
thats enough from the 'marketing corner' ... back to programming.
cheers, Jim Fuller
On Tue, Mar 24, 2009 at 10:34 PM, Guy Hulbert wrote:
> On Tue, 2009-24-03 at 21:
lwall> + enum TrigBase is export ;
Is Circles of much value?
I can see Semicircles, since that would make the range (-1,1] or [-1,1).
But a range of [0,1) or (0,1] seems *much* less useful.
Or am I missing an obvious use case?
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
1 - 100 of 156 matches
Mail list logo