Dain wrote:

> If you want method pointers today, just get a good byte code generation
> tool.

Yeah I know, and I seriously believe that workarounds such as this do more
to harm the so-called "purity" of Java than providing explicit language
level mechanisms for method pointers.

The AWT moved from Events to delegation in 1.1
Since then I have always wondered why we are compelled to delegate to
Classes implementing interfaces rather than Methods implementing specified
method signatures.

It leads to alot of structural code which obfuscates functional code, and a
lot of unnecessary plumbing to route conditional execution after the method
has been invoked.

Why can't we drop the extra structures and apply our pre-conditions before
the method is invoked?


The information in this e-mail is confidential and for use by the addressee(s) only. 
If you are not the intended recipient (or responsible for delivery of the message to 
the intended recipient) please notify us immediately on 0141 306 2050 and delete the 
message from your computer. You may not copy or forward it or use or disclose its 
contents to any other person. As Internet communications are capable of data 
corruption Student Loans Company Limited does not accept any  responsibility for 
changes made to this message after it was sent. For this reason it may be 
inappropriate to rely on advice or opinions contained in an e-mail without obtaining 
written confirmation of it. Neither Student Loans Company Limited or the sender 
accepts any liability or responsibility for viruses as it is your responsibility to 
scan attachments (if any). Opinions and views expressed in this e-mail are those of 
the sender and may not reflect the opinions and views of The Student Loans Company 

This footnote also confirms that this email message has been swept for the presence of 
computer viruses.


To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to