41. Ao.htm The Sather Programming Language, Oct93, 42; PL94, 18; Oney, Walter; Examining the Windows Setup Toolkit, Feb94, 68; Porting from DOS to Windows, Mar94, 82 http://www.cstone.net/~bachs/ddj/ao.htm

Obasanjo, Dare Ochs, Tom Review of Algorithms from P to NP, Volume I: Design and Efficiency , by B.M.E. Moret and H.D. Shapiro, Apr94, 134 Review of Programming Classics: Implementing the World's Best Algorithms , by Ian Oliver, Apr94, 133 Odette, Lou L. Computing with Streams, Sep84, 50 Nondeterministic Control Words in Forth, Sep83, 44 Z8000 Forth, Sep82, 48 Oestergaard, Rolf V. Watchdogs for Interrupt Monitoring, Jun97, 60 Offner, Rocky Oglesby, William Ellis Combining Visual Development Environments, SB.Nov/Dec96, 23 Ohlsen, Chris A Database System for Automating E-Mail, Dec90, 72 Okazaki, Taku The Windows Global EMM Import Interface, Sep94, 123 Okmianski, Anton Embedded Databases, Dec2002, 46 Oldham, C. R. OS/2 Development Tools, DU-May94, 2 O'Malley, Kevin An API for Internet Auctions (with T. Kelly), Sep98, 70 Omohundro, Stephen M. The Sather Programming Language, Oct93, 42; PL94, 18 Oney, Walter Examining the Windows Setup Toolkit, Feb94, 68 Porting from DOS to Windows, Mar94, 82 Review of Writing Windows Virtual Device Drivers , by David Thielen and Bryan Woodruff, Sep94, 129 Using DPMI to Hook Interrupts in Windows 3, Feb92, 16

42. [Mesa-dev] Re: [Mesa-bug] A Memory Bug? JeanPierre Dussault wrote Good evening! A week ago, I reported a memory bug in Mesa-3.1. Since I use Mesa from within the Sather programming language, I found it http://www.mail-archive.com/mesa-bugs@mesa3d.org/msg00128.html

mesa-bugs Thread Date Find [Mesa-dev] Re: [Mesa-bug] A memory bug? Brian Paul Sat, 2 Jan 1999 19:52:10 -0800 http://lists.mesa3d.org/mailman/listinfo/mesa-bug http://lists.mesa3d.org/mailman/listinfo/mesa-dev [Mesa-dev] [Mesa-bug] A memory bug? Jean-Pierre Dussault [Mesa-dev] Re: [Mesa-bug] A memory bug? Brian Paul [Mesa-dev] [Mesa-bug] A memory bug? Jean-Pierre Dussault Re: [Mesa-dev] [Mesa-bug] A memory bug? Brian Paul Re: [Mesa-dev] [Mesa-bug] A memory bug? Jean-Pierre Dussault Reply via email to

43. Uniform (adjective.org) This is not a feature directly supported by Java, but it is used in the Sather programming language. For example, we can look at the classes in java.io and the classes in http://adjective.sourceforge.net/uniform/user-guide/index.html

http : // www . adjective . org / Uniform Introduction Home Introduction Examples Javadoc Description Uniform is a java class library supporting runtime supertyping. In practice, that makes it somewhat like Latent Typing or Duck Typing Supertyping Most developers would be familiar with the concept of subtyping , where a new type is defined by extending (or specialising) an existing type. e.g. java.io.BufferedReader is a subtype of java.io.Reader Supertyping is the same thing, but in the opposite direction, where a new type is defined by generalising from existing types. This is not a feature directly supported by Java, but it is used in the Sather programming language For example, we can look at the classes in java.io and the classes in java.sql, and see that many of them have a method named close that takes no arguments, and returns no value. If java supported supertyping could then say: Unfortunately, java doesn't support that syntax, and the java runtime environment doesn't make it easy to add directly - i.e. You would need to modify the class files for all those types in order to add an interface to their hierarchy, and you can't reasonably do that in java. But what we can do, is make use of reflection and dynamic proxies, to add a similar feature at runtime. The uniform library refers to this as runtime supertyping Duck Typing Duck typing is a term used in the Ruby community to refer to the form of latent typing that the Ruby language implements. The basic concept is that you don't need to create a type called "Closeable" just to mark the classes that implement the close method, instead, you should write a method that says "I need an object that has a 'close' method on it". So, you define your contracts around behaviours, rather than types.

44. Steve Omohundro - The Consequences Of Very Smart Machines - QuickTopic Free Mess Among other things, he was a scientist at Thinking Machines, architected the Sather programming language, and wrote the 3D graphics portion of Wolfram's Mathematica. http://www.quicktopic.com/37/H/b4JgPdVGsn8LJ/p-1.16.1

Sign In to access your topic list New Topic My Topics Profile Upgrade to Pro ... SM Topic: Steve Omohundro - The Consequences of Very Smart Machines Views: 1335, Unique: 568 Subscribers: 1 What's this? Printer-Friendly Page Subscribe email All messages 1-5 of 5 About these ads Messages Post a new message dorkbotsf 08-01-2006 02:17 AM ET (US) Dr. Stephen Omohundro comes to us with an impressive resume. Among other things, he was a scientist at Thinking Machines, architected the Sather programming language, and wrote the 3D graphics portion of Wolfram's Mathematica. Recently Steve has been working on systems that program themselves as a vehicle to machine intelligence. Along the way, he has been thinking deeply and originally about the consequences of machines that are self-aware and self-improving. He'll talk about the psychology of these systems, how to prevent machine psychopaths, and how to create a healthy AI ecology in which human values and wisdom flourish. This promises to be a thought-provoking and exciting discussion. http://dorkbot.org/dorkbotsf/archive/200608/

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z

Page 3     41-44 of 44    Back | 1  | 2  | 3