[#5322] O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...>
I just did some benchmarks on push, pop, shift, and unshift
On Fri, 1 Jul 2005, Eric Mahurin wrote:
--- Mathieu Bouchard <matju@artengine.ca> wrote:
On Sat, 2 Jul 2005, Eric Mahurin wrote:
--- Mathieu Bouchard <matju@artengine.ca> wrote:
On Sun, 3 Jul 2005, Eric Mahurin wrote:
--- Mathieu Bouchard <matju@artengine.ca> wrote:
Hi,
--- Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
Hi,
Yukihiro Matsumoto wrote:
--- Florian Gro<florgro@gmail.com> wrote:
Eric Mahurin wrote:
--- Nikolai Weibull
Eric Mahurin wrote:
[#5388] Problem with socket communications on Windows — "Jim McMaster" <jim.mcmaster@...>
I recently installed PGP 9.0 on my Windows XP SP2 machine. At that point,
[#5391] Object#=~ — Ryan Davis <ryand-ruby@...>
Since Rexexp#=~ and String#=~ return nil if they fail to match,
Hi,
Hi,
--- Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
[#5409] socket.c - s_recvfrom — Zach Dennis <zdennis@...>
If I am reading s_recvfrom correctly in can throw an error which kills
[#5420] Sydney Developer Preview 1 released — Evan Webb <evanwebb@...>
Sydney, an experimental ruby interpreter, has been released!
Thanks everyone for the feedback so far!
Hi,
The MD5 sum is 53d1bde4542365caf4849c56e6274617.
Hi,
On 7/12/05, nobuyoshi nakada <nobuyoshi.nakada@ge.com> wrote:
Hi,
Hello,
[#5445] GC tweak — Stefan Kaes <skaes@...>
I have found that the performance of current garbage collector
[#5451] bug in pstore (ruby 1.8.2) on Windows ( Win XP) ? — noreply@...
Bugs item #2101, was opened at 2005-07-14 15:30
[#5470] Bogus age value from Etc — Daniel Berger <Daniel.Berger@...>
Hi all,
[#5471] make fail; ruby v182 not finding readline ? — OpenMacNews <OpenMacNews@...>
hi all,
[#5476] Bug in ruby's command line parsing — Lothar Scholz <mailinglists@...>
Hello,
On Sat, Jul 16, 2005 at 10:11:34AM +0900, Lothar Scholz wrote:
[#5492] ruby ( v183) bcc32: using Socket.new with timeout -> files not closed — noreply@...
Bugs item #2131, was opened at 2005-07-19 17:34
Re: Subversion
On Jun 30, 2005, at 5:29 PM, Shugo Maeda wrote: >> I wouldn't say subversion is better yet, just different. > > I think good points of Subversion are: > > : Not based on single file > CVS is based on single file, and doesn't support rename and > removal > well. Subversion gives a revision to changes in all related > changes > per commit, so it's easy to track changes. > : Security > Subversion is not perfect, but more secure than CVS. > We can use HTTPS and basic auth, so committers doesn't need > Unix accounts any more, and extra ports like pserver are not > necessary. > : Easy to maintain > The complexity of loginfo of CVS is my headache. (I think it's > also > eban's headache) > post-commit of Subversion and `svnadmin dump' is easy to use. > `svnadmin dump' also supports incemental backup. > : Trac > Trac (http://www.edgewall.com/trac/) is an issue tracking system. > Trac and Subversion are good friends. We can close a bug just to > write a ticket number in a commit log like: > > fixed something. (closes #1234) > > Trac has also a good repository browser for Subversion. > Please see http://dev.rubyonrails.com/ for example. *nod* These are all very good points, and with the exception of trac (although there is an open bug on this exception), all of these points are also supported by perforce. Perforce is free for open- source development and is used by larger groups like freebsd (http:// perforce.freebsd.org/). The clients are free to anyone and available on just about every version of every OS under the sun. It also has some other benefits: + Some commands/options just seem so much more straightforward (p4 sync -n to see what you WOULD get if you sync'd, not svn -u st). At least they do to me. + Merging is much easier + Much more uniform use of revision identifiers across nearly all commands + Repository diffs are FAST (10x faster by my unscientific measure). + p4 opened -a (who has what open?) is _awesome_. + p4 describe $revision is _awesome_ (and much much faster than the equivalent in svn). + underneath it all, still rcs files, no binary DB to corrupt (there are binary DBs for metadata) + Proven scalability. + Much more mature and bug free.