$B$^$D$b$H(B $B$f$-$R$m$G$9(B
In message “Re: [ruby-dev:43653] Re: DateTime.new! and DateTime.jd”
on Wed, 8 Jun 2011 02:29:15 +0900, Aaron P.
[email protected] writes:
|1.9.2$B$G$O$3$N%3!<%I$,:nF0$7$?$K$b4X$o$i$:!"(B1.9.3$B$G$O:nF0$7$J$$$N$,;v<B$G$9!#(B
|$B$3$NJQ99$K4X$7$F$N%G%#%W%j%1!<%7%g%s$N7Y9p!“0\E>!?0\F0!J!)!K%3!<%I$N;X<($J$I2?$b8+<u$1$i$l$^$;$s$N$G!”(B
|$B$3$l$,%P%0$+!"H]$+$O;d$K$OH=CG$G$-$^$;$s!#(B
[email protected]$N%a!<%k$K$b=q$$$?DL$j!";d$,!"$U$J$P$5$s$N0U?^[email protected]$7$/M}2r(B
$B$7$F$$$k$J$i$P!"$I$A$i$b%P%0$G$O$J$/!“K\Mh$N;EMM$r30$l$?;H$$(B
$BJ}$,$G$-$J$/[email protected]$H$$$&$3$H$J$N$G!”:n<[email protected]$+$i$$$&$H(B
$B%P%0$G$O$J$$$H$$$&[email protected]$H;W$$$^$9!#(B
[En]
As I stated before, if I understand him correctly, both
“problems” are not caused by bugs, but by changes to
internal behavior, which should not be used at first. So
from the author’s point of view, they are not bugs of date
library.
|$B%3%%C%H%a%C%;!<%8(B(r31862 and
r31668)$B!!$K$b!V5!G=$N:o=|!W$K4X$7$F5-$5$l$F$$$^$;$s$G$7$?!#(B
|$B$b$7$3$NF0:n$,GQ;!?:o=|$5$l$F$$$k$N$G$"$l$P!“2?$rBeMQ$K;H$($PNI$$$+(B
|$B65$([email protected]$1$^$;$s$+!)(B
|
|$B;d$N:G=L\E$O$3$N%3!<%[email protected]!”%F%9%H40N;$G$9$N$G(B
|$BF0:n$,GQ;_!?:o=|$5$l$F$$$k$3$H<[email protected]$J$I$O$"$j$^$;$s!#(B
date$B%i%$%V%i%j$NL$8x3+(BAPI/$BL$Dj5A$NF0:n$K0MB8$7$F$$$?%3!<%I$,(B
$BB8:_$7$F$$$?$H$$$&$3$H$G$9$+$i!"4JC1$K!VBeMQ!W$,8+$D$+$k$H$O(B
$B8B$j$^$;$s!#$7$+$7!"LdBj2r7h$K6(NO$O$7$?$$$N$G!“6qBNE*$K$I$N(B
$B%i%$%V%i%j$r$I$N$h$&$K;H$C$?$H$-$K!”$I$N$h$&$JLdBj$,@8$8$F$$(B
$B$k$+65$([email protected]$1$^$;$s$+!)(B
[En]
That means some gems appear to rely on date’s internal API
or undefined behavior, so that there might not be easy
“replacement”. But we’d like to help. Could you tell me
what gems cause what kind of problem, preferably in detail,
instead of reporting bugs in date library?
$B$^$D$b$H(B $B$f$-$R$m(B /:|)