Crispin Cowan wrote:
Al Eridani wrote:
On 11/9/06, Crispin Cowan [EMAIL PROTECTED] wrote:
Prior to Java, resorting to compiling to byte code (e.g. P-code back in
the Pascal days) was considered a lame kludge because the language
developers couldn't be bothered to write a real compiler.
On 11/13/06, Glenn and Mary Everhart [EMAIL PROTECTED] wrote:
Crispin Cowan wrote:
Al Eridani wrote:
On 11/9/06, Crispin Cowan [EMAIL PROTECTED] wrote:
Prior to Java, resorting to compiling to byte code (e.g. P-code back in
the Pascal days) was considered a lame kludge because the
At 10:31 PM +1100 11/13/06, mikeiscool wrote:
On 11/13/06, Glenn and Mary Everhart [EMAIL PROTECTED] wrote:
If there is some construct that NEEDS to be interpreted to gain something, it
can be justified on that basis. Using interpretive runtimes just to link
languages, or just to achieve
I have released a new document 'Challenges faced by automated web application
security assessment tools' that a few of you
may find interesting.
URL:
http://www.cgisecurity.com/articles/scannerchallenges.shtml
Comments welcome.
- Robert
http://www.cgisecurity.com/ Website Security news,
On 11/14/06, ljknews [EMAIL PROTECTED] wrote:
At 10:31 PM +1100 11/13/06, mikeiscool wrote:
On 11/13/06, Glenn and Mary Everhart [EMAIL PROTECTED] wrote:
If there is some construct that NEEDS to be interpreted to gain something,
it
can be justified on that basis. Using interpretive
David A. Wheeler wrote:
On 11/9/06, Crispin Cowan [EMAIL PROTECTED] wrote:
Prior to Java, resorting to compiling to byte code (e.g. P-code back in
the Pascal days) was considered a lame kludge because the language
developers couldn't be bothered to write a real compiler.
I believe
On 11/14/06, Leichter, Jerry [EMAIL PROTECTED] wrote:
| If there is some construct that NEEDS to be interpreted to gain
| something, it can be justified on that basis. Using interpretive
| runtimes just to link languages, or just to achieve portability
| when source code portability
mikeiscool wrote:
On 11/14/06, Leichter, Jerry [EMAIL PROTECTED] wrote:
The joke we used to make was: The promise of Java was Write once,
run everywhere. What we found was Write once, debug everywhere.
Then came the Swing patches, which would cause old bugs to re-appear,
or suddenly
