search for: disincentive

> If they choose to continue with only EXE, > I will just keep using other programming languages. I did agree with your original suggestion. However, I don't think that a lack of zip formats, is a disincentive from using R. If you have an issue with the Windows installer, the obvious option is to install the source version, and compile from it. This is, after all, how open source is designed to work. Also, I agree with what Duncan said. Abs [[alternative HTML version deleted]]

...time. Moreover, ideas that were wrong 20 years ago may very well be right today. The combination of the current "10% or better" practice with no requirement for reproducibility means there's very little incentive to release tools and code used for the experiments. In fact there is disincentive, as we wouldn't want some precocious student to demonstrate the experiment was flawed. This is another problem, in that researchers view challenges as personal threats rather than a chance to advance the state of the art and students are encouraged to combatively challenge published resear...

...pport distributed development support this kind of scenario. > So, what exactly are people finding wrong with CVS on a day to day > basis, and is it important enough to fix it (fixing it will mean that > users will need to download a new program to use the repository, which > is a disincentive to using LLVM)? There you have it, this is what I find wrong with CVS on a day to day basis. If it's important enough to fix it is up to the oversight comittee to decide ;-) By the way, the LLVM _users_ are supposed to use the releases which are distributes as tarballs, and have no need to...

...ing else looks like something that would be nice to have, but isn't critical. So, what exactly are people finding wrong with CVS on a day to day basis, and is it important enough to fix it (fixing it will mean that users will need to download a new program to use the repository, which is a disincentive to using LLVM)? -- John T. > > If you're interested in this topic (and you should be if you're actively > developing), please have a look at this site: > _http://better-scm.berlios.de/comparison/comparison.html_ > <http://better-scm.berlios.de/comparison/comparison.h...

...ll make it actually work correctly. If we start adjusting for its quirks now, we can (hopefully) have something reasonably stable by the time lots of Win32 people start using LLVM. > > And for those without an MSDN subscription, the cost of purchasing the > latest Visual Studio is enough disincentive. Another reason why I suggested the free download alternative ;> > If the LLVM code base doesn't want to compile with VC++ 6 because it's > not sufficiently ANSI compliant, that's a good enough reason to not > support it. That's exactly the reason. > I know that...

...est VC++ (still a problem with 7.1). And don't even think of doing this near the end of a release cycle for your product. The mere thought of using a /beta/ version of a Microsoft product... And for those without an MSDN subscription, the cost of purchasing the latest Visual Studio is enough disincentive. If the LLVM code base doesn't want to compile with VC++ 6 because it's not sufficiently ANSI compliant, that's a good enough reason to not support it. I know that template support wasn't very compliant with 6 (though still better than most non-g++ Unix compilers even today) and L...

On Wed, 2004-09-15 at 00:17, Paolo Invernizzi wrote: > On Sep 15, 2004, at 8:40 AM, Henrik Bach wrote: > > > Hi, > > > > Has some one committed these patches into CVS? > > Not yet... checked 10 minutes ago... Hopefully Chris will get to it today (Wednesday). > I'm attaching the cvs diff -u version of them (I've read Reid Spencer > post about it)

...ubqueue we now have constant per sub-subqueue, so something like 128 => 128 x 20) - double the time for two lookups - nontrivial change in code. Of course, the temptation would be to make the code work with n levels. So far I''ve been able to get by without it. That, along with the disincentives above account for it remaining on the queue for so long. Some day I''ll need it. If I''m lucky someone else will get there before me.

...our boot partition in order to uninstall beta versions of VS. And, of course, it is required that you uninstall the beta before installing a newer beta or the release version. > > And for those without an MSDN subscription, the cost of purchasing the > > latest Visual Studio is enough disincentive. > > Another reason why I suggested the free download alternative ;> It's only free until enough bugs have been fixed to justify charging for it :) > I think you're right that "standardization" on the VC 8 compiler is > somewhat risky. We should continue the 7.1...

Hello, I posted a question yesterday but I got no replies, so I'll try to reformulate it in a more concise way. I have the following data, summarizing approval ratings on two different surveys for a random sample of 1600 individuals: > ## Example: Ratings of prime minister (Agresti, Table 12.1, p.494) > rating <- matrix(c(794, 86, 150, 570), 2, 2) > dimnames(rating) <-

...be ordered by merge, or specifically, a pre-order, depth-first traversal of the commit tree. I believe people care more about when the patch entered their own repository than when the author made the commit to his or hers. Proposal: a slow, multistep, backward-compatible transition to remove the disincentive to contribute patches from private forks: Step 1: Demonstrate "git log" or a similar tool can produce a linear history in the presence of merging. This may already be possible. Step 2: Swap the roles of git and svn. Make svn the mirror and git the central repository, and update the on...

...merous groups (including mine) working with LLVM without any problem due to this. There are even several that *do* have some code which doesn't go upstream, and they also are not thwarted by this. <snip> > Proposal: a slow, multistep, backward-compatible transition to remove > the disincentive to contribute patches from private forks: I strongly doubt that this is the primary barrier for the contribution of such patches. Code review, the fact that these patches have accreted for long periods of time outside the view of the community, and a lack (or broken nature) of incremental developm...

On Mon, Jun 3, 2019 at 8:04 PM Duncan Murdoch wrote: > I don't recall anyone asking for the zip in the 17 years after that > change, until now (though I haven't been paying attention lately, since > I retired from building the binaries a couple of years ago). > > If you think it's worthwhile to do it, then I don't think anyone would > object if you went ahead and

...that would be nice to have, but > isn't critical. > > So, what exactly are people finding wrong with CVS on a day to day > basis, and is it important enough to fix it (fixing it will mean that > users will need to download a new program to use the repository, which > is a disincentive to using LLVM)? > > -- John T. > > > > > If you're interested in this topic (and you should be if you're actively > > developing), please have a look at this site: > > _http://better-scm.berlios.de/comparison/comparison.html_ > > <http://better...

...a were good, but I'm really concerned about this apparent inability to handle heavy loads. Has anyone seen this kind of behaviour, or can anyone suggest any workarounds? Thanks, Tony -- Tony Gray, Technical Services Manager, School of Computing University of Tasmania -- "Imagine the disincentive to software development if after months of work another company could come along and copy your work and market it under its own name...without legal restraints to such copying, companies like Apple could not afford to advance the state of the art." -- Bill Gates (New York Times, 25 Sep 1983).

...se case, and it is important > to sample pgo too. That's why I proposed to have " duplicated code > that may have different execution count" being recorded. Will that > suffice to get the info you want? (i.e. for every version of the > multi-versioned loop, you will have a disincentive discriminator > associated with all the code it expands. I don't know. Can you explain how the process will work? By the time the code/metadata arrives at, say, the loop vectorizer, how can we tell whether the vectorized version we might now create will be executed (based on having profiling...

...e nice to have, but } > isn't critical. } > } > So, what exactly are people finding wrong with CVS on a day to day } > basis, and is it important enough to fix it (fixing it will mean that } > users will need to download a new program to use the repository, which } > is a disincentive to using LLVM)? } > } > -- John T. } > } > > } > > If you're interested in this topic (and you should be if you're actively } > > developing), please have a look at this site: } > > _http://better-scm.berlios.de/comparison/comparison.html_ } > > &...

LLVMers, The oversight group has been kicking around the idea of getting a better version control system than CVS. The problem is, we're not quite sure what "better" means. So, we thought we'd ask your opinions. If you're interested in this topic (and you should be if you're actively developing), please have a look at this site:

On Sunday 28 March 2010 16:39:44 llvmdev at erichocean.oib.com wrote: > To the list: > > Tons of LLVM research is being done that is damn near worthless to anyone > but the person who did it because the team doesn't publish supporting code > or even describe at a high level description of the algorithms they're > using. And the excuse is always, ALWAYS the same:

...9;s why I proposed to have " duplicated > > > code > > > that may have different execution count" being recorded. Will > > > that > > > suffice to get the info you want? (i.e. for every version of the > > > multi-versioned loop, you will have a disincentive discriminator > > > associated with all the code it expands. > > > > > I don't know. Can you explain how the process will work? By the > > time > > the code/metadata arrives at, say, the loop vectorizer, how can we > > tell whether the vectorized vers...