Re: question on java lang spec chapter 3.3 (unicode char lexing)

From:

=?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>

Newsgroups:

comp.lang.java.programmer

Date:

Wed, 02 Jan 2013 21:12:25 -0500

Message-ID:

<50e4e90c$0$286$14726298@news.sunsite.dk>

On 1/2/2013 9:02 PM, Aryeh M. Friedman wrote:

On Wednesday, January 2, 2013 8:55:19 PM UTC-5, Aryeh M. Friedman

Aegis/cook (aegis.sf.net) and the issue is not the build system per
se but how most build system deals the split source view aegis
provides (which the aegis documentation correctly points out
*ALMOST* no build system deals with correctly except for cook)...
i.e. every build system makes the assumes that there is a single
definition of each compilation unit where aegis makes it so the
current version and all previous versions are available (this makes
tracking what changes have been made much easier then say
cvs/svn/git besides none of them are truly atomic interms of
commits {you have to prove your code works before committing it and
this is enforced by the VC system).

Also cook is the only build system (besides make) that I have dealt
that does not make extremely hard and often incorrect assumptions
about your environment for example ant/maven/etc. are a nightmare for
anything besides Java (we often have 2 or 3 langs in one project)

Ant and maven are designed for Java. They work fine for Java and
Java compatible languages.

They may not work great for completely unrelated languages.

But they can activate other build systems and most other build
systems can activate them.

and
very often the assume your using a IDE (and often a specific one)

ant and maven does not make such assumption.

where we do all our work from the command line by company policy (we
have never found a IDE that correctly handles stuff like making
completely standalone executable jars and such)

All Java IDE's that I know can do that.

So can ant and maven.

Arne