Beefy Boxes and Bandwidth Generously Provided by pair Networks vroom
Syntactic Confectionery Delight
 
PerlMonks  

Re^6: Precedence design question...'x' & arith

by perl-diddler (Friar)
on Jul 06, 2013 at 06:44 UTC ( #1042858=note: print w/ replies, xml ) Need Help??


in reply to Re^5: Precedence design question...'x' & arith
in thread Precedence design question...'x' & arith

You go on and on, about what might happen, but can't come up with one example where it is a problem? Are you familiar with the term F.U.D.?

I can see now that you don't care to prove your point, by providing any concrete examples that would show me the follow of my ways -- you just wish to say 'no' and think that this isn't thought out. The more you argue the point without coming up with any good reasons why it's a problem the more you are making the argument that this issue is being well vetted.
------------------------

Leaving original content above for reference.

I asked a question what would happen or what would be the impact of a particular design change. Instead of any specific examples, I got FUD.

On top of that people actually got annoyed when I called the morass of negativity that spewed out what it was -- in light of there being no cases to support any problems.

Someone else claims burden of proof is on person advocating for change.

I examined the possible cases -- noted that the only behavior change would be to allow a useful behavior in what previously would fail.

That is the proof. Before, with no change, nothing worked -- it fails. With the change, you get useful, positive behavior. So in ANY use case, at worst, you could get some other failure and be no worse off than before.

But with the change, you get positive and useful output.

How can you call that an absence of proof?


Comment on Re^6: Precedence design question...'x' & arith
Re^7: Precedence design question...'x' & arith
by davido (Archbishop) on Jul 06, 2013 at 07:02 UTC

    I think the burden of proof is really upon the person advocating for the change.

    If it's worth it to you, fork the Perl repository. Apply a patch and associated tests that make the change. Set up two smokers -- One with the Perl version that you forked, and one with the Perl version that you patched. Smoke test as much of CPAN as you can in two weeks time. Demonstrate that there were no FAILs under your patched Perl except for ones that also existed under the unaltered Perl.

    Meanwhile, join in at the P5P mailing list. Demonstrate the patch to them, and explain that you're in the process of smoking it against CPAN now. See if you can arouse any interest from the people with commit bits.

    If both your testing, and your salesmanship are successful, you will get your name in the POD for an upcoming release of Perl.


    Dave

      The first part of your idea is good... will have to see how I can do that considering perl won't build on my machine (the DB stuff doesn't pass)...

      The 2nd part... I'm not welcome on the P5P list. Their comments are that while I may be polite, I don't say things they find pleasant. Unfortunately, they prefer pollyannaish pleasantries over factual discourse. Some things are difficult if not impossible to make 'pleasant' and as an engineer and scientist, I tend to look at why things are the way they are and look for how to make them better -- not accepting the status quo, because I know it isn't good enough -- that makes me oh, so popular. It's not that what has come before was bad.. it's that it can be better, with almost everything having been built on that which came before.

      But some take the attitude that what came before is perfect as it is, which shows what? If it was perfect as it is, everyone would flock to "it" (whatever it is) or it would make everyone's life easier.

      One thing I don't like about perl is all the damn sigils. There are MANY places where they are redundant. So why require require them? I would NOT say prohibit them, -- as there are many places where you may have the same named variable/subs and the sigil is the only thing differentiating them. But if you only have 1 type of a name, say a scalar 'x', why not just say x=1?, or if I say carton2=1, isn't is clear from the context that carton must be an array? Those are other examples where something could be meaningful syntax, that makes unequivocal and unique sense that for no reason other than "the rules" has been declared illegal syntax. It can't be incompatible with past programs -- like the suggested change of this base-subject, because it is *illegal* syntax under the current perl.

      If we took all the cases of illegal syntax and put them to use *where it made sense*, we'd end up with a more powerful language "for free"... It would still run the old perl5 programs, but allow for a whole new set of expressions that take less work to express.

      If you read any articles on language design (like the one I've quoted and linked to earlier in this conversation), you'll quickly see that *conciseness* is directly proportional to power in a language. The fewer characters (even by 2 parenthesis), that you can say something, the more powerful the language is and the easier it is for people to express ideas in it.

      It's the same in spoken language. If there is no word for an idea, it is hard to talk about it ... you can create sentences or paragraphs to describe or talk around it, but until you have a work for an idea, it's hard to grasp onto. The fewer symbols needed to describe an idea, the easier it is to get across meaning.

      As for the p5p list.... I told a story from a driver's ed class about someone who grew up in an area and didn't want to change -- while the world changed around him and how it, in the limit could even cause fatal results. The p5p found that story so offensive, they kicked me off the list. Now I know the story wasn't inherently offensive -- it was told to a public audience in a public class and no one was offended, but in the p5p bunch, they took it as some indictment worth of excising me from the list. Go figger. I figured, if it wasn't that it would be how I styled my hair - - they were just looking for a reason -- any reason would do. Recently they had a fit because of a reply in kind to a trite closing of one of my bugs. Yet if you read what I wrote, the reaction was WAY over the top.

      It's clear there isn't much I can say that isn't colored and taken a certain way -- look at how this question started off -- one of the first replies, "G'day", accused me of lying as to my reasons for wanting this change. That I'd made a coding error and wanted to change perl because of it. I've been coding in perl for over 20 years. _EVEN_ if I made such a mistake after 20 years of doing this (which I didn't, I want'ed to get rid of the parens), don't I have the right, to ask why it is that way and why it couldn't be better? If it could, why do others take such a negative attitude toward improvement?

      At least you have the positive idea of making the changes and running the tests... which is a huge leap above most other replies -- yours is practical and concrete. For that I thank you. (Despite the difficulties I may have in implementing the ideas--;-)).

        The fewer symbols needed to describe an idea, the easier it is to get across meaning.
        Have you ever tried to read APL?
Re^7: Precedence design question...'x' & arith
by BrowserUk (Pope) on Jul 06, 2013 at 09:38 UTC
    You go on and on, about what might happen,

    No I didn't.

    but can't come up with one example where it is a problem?

    I didn't attempt to.

    Are you familiar with the term F.U.D.?

    Yes. Very.

    I can see now that you don't care to prove your point, ... you just wish to say 'no' and think that this isn't thought out.

    Well done, you can read! That is exactly what I wrote, and the exact message I intended to convey.

    The more you argue the point ...

    Aah! Then again, maybe you can't...:(

    I give no argument because it isn't worth the effort. I simple expressed my opinion to that effect..

    I have zero say over whether this gets implemented so, you're 5 minute argument is over for lack of interest.


    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1042858]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (12)
As of 2014-04-19 05:37 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (478 votes), past polls