Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Shawn Wagner <shawnw@speakeasy.org>
To: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] help
Date: Fri, 16 Apr 2004 17:34:42 -0700	[thread overview]
Message-ID: <20040417003442.GA848@speakeasy.org> (raw)
In-Reply-To: <1082141984.20063.184.camel@pelican.wigram>

On Sat, Apr 17, 2004 at 04:59:45AM +1000, skaller wrote:
> On Sat, 2004-04-17 at 04:04, mohammad siddiqui wrote:
> > Hi,
> > I started the conversion project after completely getting hold of ocaml but 
> > I still have some concerns like how we can manage pinters and pointer to 
> > pointers,
> 
> Generally you don't need them. Here is an example: in C:
> 
> struct ilist { list *next; int v; };
> 
> In Ocaml:
> 
> type ilist = Cons of int * ilist | Empty

This seems like a bad example, as you're just reinventing int list with it.

C pointers are something like ocaml references.

C: int *foo = &bar;
   *foo = 12;
   printf("%d", *foo);

Ocaml: let foo = ref bar in
        foo := 12;
	Printf.printf "%d" !foo
	
except that the value of bar won't be changed in the latter.	

> 
> >  some functions in C like exit(), isspace().
> 
> exception Exit
> The Exit exception is not raised by any library function. It is provided
> for use in your programs.

There's also the exit function, which does the same thing as C exit(), and
doesn't cause a message about an uncaught exception...

> 
> isspace is easy to implement:
> 
> let isspace = function
> | ' ' | '\t' -> true
> | _ -> false

\r, \n and some other characters also count as whitespace. The C character
classification routines (isspace, isalpha, etc.) are part of extlib.

-- 
Shawn Wagner
shawnw@speakeasy.org

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2004-04-17  0:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 18:04 mohammad siddiqui
2004-04-16 18:59 ` skaller
2004-04-17  0:34   ` Shawn Wagner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-25 16:30 mohammad siddiqui
2004-04-25  1:53 ` mohammad siddiqui
2004-04-25 12:13   ` Jon Harrop
2004-04-25 12:45     ` Henri DF
2004-04-26 19:13       ` Jon Harrop
2004-04-26 22:38         ` Andrew Lenharth
2004-04-25 17:28   ` Matt Gushee
2004-04-25 17:06 ` Jon Harrop
2004-04-25 17:39   ` Matt Gushee
2004-04-26  0:45 ` skaller
2004-04-23  2:31 mohammad siddiqui
2004-04-23  4:17 ` Jon Harrop
2004-04-23  6:52   ` Jean-Christophe Filliatre
2004-04-23 15:43 ` Brian Hurt
2004-04-22 23:34 mohammad siddiqui
2004-04-22 23:57 ` Karl Zilles
2004-04-08 22:57 mohammad siddiqui
2004-04-09  6:56 ` Basile STARYNKEVITCH
2004-04-09  9:04 ` Richard Jones
2002-11-05 12:22 ÀîÒÇ
2002-11-05 13:39 ` Alessandro Baretta

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=20040417003442.GA848@speakeasy.org \
    --to=shawnw@speakeasy.org \
    --cc=caml-list@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