graydon hoare [EMAIL PROTECTED] wrote on Wed, 26 Nov 2003 22:40:18 -0500:
[many proposals for testing]
IMHO, most proposals sound very convincing.
- tests can be added inline with a source file, or right next
door in a similarly-named class or package.
I guess my point is I'd
Hi,
configure.in had the following macro definitions:
AC_CYGWIN
AC_MINGW32
The Autoconf manual says they are deprecated and all autotools complain
loudly about their usage. Since I couldn't find a real reason for using
them I just removed them for now. Do we actually have people compiling
Hi all,
[UPDATE: It appears I broke it :( I am trying to figure out what I did
wrong. Help wanted...]
Patrik Reali (of Joas fame) was so kind to update our webpages. He is
playing in the mountains at the moment (he will be back in two weeks).
So I committed them. All praise should go to Patrik,
Hi,
On Thu, 2003-11-27 at 16:57, Mark Wielaard wrote:
[UPDATE: It appears I broke it :( I am trying to figure out what I did
wrong. Help wanted...]
Somehow this fixed itself. Strange. I have been banging my head against
a wall for an hour and apparently some cron job then kicked in and
Hi,
Here is a new part of the patch for serialization. It is mainly about
restructuring the class lookup logic. It appeared that you need to build
a class lookup table and a class hierarchy for a given input stream.
Without that, if you write something with ObjectOutputStream and then
read
Hi,
On Thu, 2003-11-27 at 17:12, Mark Wielaard wrote:
Anyway. Please check out Patrik his work:
http://www.gnu.org/software/classpath/
BTW. Savannah was also recently upgraded.
You might want to take a look at
http://savannah.gnu.org/
An overview of the user interface changes can be found in
David Bélanger wrote:
I think Etienne did these two changes, I'm not sure. Maybe Etienne
could answer your questions on these.
java_io_File.c: Basically, it frees a local ref, I guess otherwise it may
run out of local refs for a long directory listing.
(*env)-SetObjectArrayElement(env,
Hi,
: == Mark Wielaard [EMAIL PROTECTED] writes:
: Looked some more at the code and I see now that the the first change was
: inside a if (time = gregorianCutover) so it now makes more sense to me.
: And the second change seems correct given the above remark.
: I'll commit it in Classpath.
Hi,
Browsing GNU Classpath's CVS log, I found:
2003-10-02 Michael Koch [EMAIL PROTECTED]
* java/text/SimpleDateFormat.java
(compileFormat): Character.isLetter(char) allows too much characters.
Replace it with Character.isLowerCase(char) ||
On Fri, Nov 28, 2003 at 01:06:43AM +0900, Ito Kazumitsu wrote:
Hi,
Browsing GNU Classpath's CVS log, I found:
2003-10-02 Michael Koch [EMAIL PROTECTED]
* java/text/SimpleDateFormat.java
(compileFormat): Character.isLetter(char) allows too much characters.
Hi,
: == Michael Koch [EMAIL PROTECTED] writes:
I am afraid Character.isLowerCase(char) || Character.isUpperCase(char)
also allows too many characters, including Greek or Slavic alphabet
or even Japanese Zenkaku alphabet.
: Grrr! I thought its the same. All I found int the docs indicated
[EMAIL PROTECTED] said:
A mauve test attached. Since I have got a write access to the mauve
CVS registry, I will add it to the registry. The test results shows
that Sun's implementation also seems to have something wrong.
If Sun's implementation (you don't say which JDK version!) is
Hi,
On Fri, 2003-11-28 at 02:03, Stephen Crawley wrote:
The over-arching principle for Mauve testcases is that the behavior of
Sun's Java implementations is the gold standard for conformance
testing.
I don't agree. We should not create Mauve tests to validate some
proprietary library
Mark Wielaard [EMAIL PROTECTED] wrote:
On Fri, 2003-11-28 at 02:03, Stephen Crawley wrote:
The over-arching principle for Mauve testcases is that the behavior of
Sun's Java implementations is the gold standard for conformance
testing.
I don't agree. We should not create Mauve tests to
14 matches
Mail list logo
