My code is a mess, please help!
If any of you have been foolish^Wbrave enough to look at the CPANdeps source code, you will no doubt have recoiled in horror. That's what happens when a quick hack that works gets put into production, then has features added, and becomes popular, gets some needed performance tweaks, and so on. It needs a gigantic re-factor. Other than the Mark 1 Eyeball, can anyone recommend any tools for finding duplicated chunks of code? Perhaps something using PPI, as that should be able to cope with varying whitespace/variable names between the duplicated chunks. -- David Cantrell | Cake Smuggler Extraordinaire Aluminum makes a nice hat. All paranoids will tell you that. But what most do not know Is reflections will show On the CIA's evil landsat.
Re: My code is a mess, please help!
David Cantrell wrote: If any of you have been foolish^Wbrave enough to look at the CPANdeps source code, you will no doubt have recoiled in horror. That's what happens when a quick hack that works gets put into production, then has features added, and becomes popular, gets some needed performance tweaks, and so on. It needs a gigantic re-factor. Other than the Mark 1 Eyeball, can anyone recommend any tools for finding duplicated chunks of code? Perhaps something using PPI, as that should be able to cope with varying whitespace/variable names between the duplicated chunks. I've yet to have a chance to play with it but this might be of use. http://unique.sourceforge.net/ Mike Woods Full of squishy cynicism
Re: Fun Friday afternoon topic: domain name disputes
On 5 February 2010 15:19, Elizabeth Mattijsen l...@dijkmat.nl wrote: If it would be a co.uk domain, she could probably go to a UK court. Since this is a .com domain, I think any UK judge will quickly dismiss on the grounds that it is an American domain, so that she should go to court in the U.S. of A. And *that* will prove to become very costly very quickly indeed. no .co.us would be an american domain, .com is a global TLD, so it's anybodies. OTOH, national businesses using an global TLD is hateful. A. -- Aaron J Trevena, BSc Hons http://www.aarontrevena.co.uk LAMP System Integration, Development and Consulting
Re: Fun Friday afternoon topic: domain name disputes
On Tue, Feb 9, 2010 at 15:46, Aaron Trevena aaron.trev...@gmail.com wrote: no .co.us would be an american domain , specifically one for a company in Colorado. Or so it used to be; I think they've relaxed the rules on the .us domain since then. (Perhaps partly because the strict rules were, I believe, one reason why the .us TLD never really caught on.) Cheers, Philip -- Philip Newton philip.new...@gmail.com
Re: Fun Friday afternoon topic: domain name disputes
On Tue, 2010-02-09 at 14:46 +, Aaron Trevena wrote: If it would be a co.uk domain, she could probably go to a UK court. Since this is a .com domain, I think any UK judge will quickly dismiss on the grounds that it is an American domain, so that she should go to court in the U.S. of A. And *that* will prove to become very costly very quickly indeed. no .co.us would be an american domain, .com is a global TLD, so it's anybodies. That's true but only to a limited extent as .COM domains are registered subject to the terms and conditions of the ICANN approved registries which pretty much all state that legal disputes regarding the domain registration must be settled in the courts of that registries home country or, more commonly, in the USA. Certainly a judge in an English (and Welsh) or Scots court would not refuse to hear a case arising from a dispute but if the other party responds to the case pointing out that the domain is registered subject to the laws of some other jurisdiction the judge may decide that it's appropriate to direct the plaintiff to bring the case there. That said the court is just as likely to hear the case and make an order on the basis that the order should be enforceable through the courts of the other jurisdiction. OTOH, national businesses using an global TLD is hateful. Why? The global TLDs are not reserved to multinationals. They are, rightly, first come first served subject to reasonable restrictions in law - ie trademark, etc.