caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] OCaml && COCOA-Environment (Mac-OS-X/GUI)
Date: Tue, 22 Feb 2005 11:54:34 +0100	[thread overview]
Message-ID: <20050222105434.GA571@first.in-berlin.de> (raw)
In-Reply-To: <a289eb671c5bceded4f3046e3c13eada@fas.harvard.edu>

On Sat, Feb 05, 2005 at 02:51:20PM -0500, Mike Hamburg wrote:
[...]
> knowledge could resurrect it.  The existing code is not strongly typed: 
> you can attempt to pass the wrong number or type of arguments to a 
> method, and it will raise an O'Caml exception instead of rejecting it 
> at compile time.
[...]


The big advantage in flexibility is the big disadvantage in
secure programming: The late binding of Objective-C seems
to be a good thing for many people and many tasks, because
runtime loading of code means a lot of flexibility.
But as I started to jump into ObjC in more detail during the last
few weeks, with one of my first examples I run into that advangage's
traplike behaviour: Compiling code was done without any errors/warnings.
After running the code, I got the message that the program could not
run one of the methods...

...this was in a really small example. And this is, where the static
behaviour of OCaml has told me that something was wrong.
When extrapolate this late binding problem to bigger, big,
huge, very huge code base, then it is clear to me, what aproach
will yield to safer programming and faster programming (because
you don't need to test the running program to find, what you
also have found earlier - during compilation time).


Nevertheless yields ObjC-programming (because of it's flexibility)
very short development times.

But Ocaml also yields to rapid development. :)

One big advantage - at least in the COCOA-environment - is,
that ObjC can use a lot of powerful libraries.
This also is a reason for rapid developement, so it's not only
the language itself.

OK, long words for what I started to say here: The problem with
exceptions instead of compile-time errors may be caused by using
the id-type instead of statically using specialized types for the
object-allocation?!


Maybe it would be a good idea to write an OCaml-program that
generates the glue-code between OCaml and ObjC/COCOA?!


Ciao,
   Oliver


      parent reply	other threads:[~2005-02-22 23:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-05  0:02 Oliver Bandel
2005-02-05 16:37 ` [Caml-list] " Julien Roussel
2005-02-05 19:51   ` Mike Hamburg
2005-02-06 21:04     ` Paul Snively
2005-02-07  2:24       ` Oliver Bandel
2005-02-09 19:41         ` Mike Hamburg
2005-02-17  7:12       ` Jeff Henrikson
2005-02-18 23:41         ` [Caml-list] " art yerkes
2005-02-25  2:03         ` Paul Snively
2005-02-25  9:13           ` Oliver Bandel
2005-02-26  1:19             ` [Caml-list] " Sachin Shah
2005-03-01  6:39           ` Jeff Henrikson
2005-03-07  5:20             ` Paul Snively
2005-02-22  2:45     ` [Caml-list] " William D.Neumann
2005-02-23  0:12       ` Jacques Garrigue
2005-02-24 20:40         ` Paul Snively
2005-02-24 23:21           ` Oliver Bandel
2005-02-25 17:20             ` Mostly OT: Apple and Language Adoption was " Paul Snively
2005-02-22 10:54     ` Oliver Bandel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050222105434.GA571@first.in-berlin.de \
    --to=oliver@first.in-berlin.de \
    --cc=caml-list@yquem.inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).