caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: RE: [Caml-list] Who controls INRIA mailserv filters?
Date: Thu, 12 Aug 2004 02:22:56 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDKEFFHGAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <Pine.A41.4.44.0408121018220.372838-100000@ibm1>

Diego Olivier
>
> When I recommend you to make your post more technical it means :
>
> - adding blocks of Caml code in your signature instead of the current
> one that just says the Caml filter is a crap (exercice : make a Caml
> program that chooses randomly 20 lines of code in the Caml compiler
> and adds them to your signature)

Not a bad idea, and less audacious than using Xavier as my trojan.  :-)
Testfiring now.

> - using more specifically Caml oriented words - something like "In the
> next Seattle meeting we will discuss how inclusion polymorphism /
> functors < add technical content here > can be applied to 3D rendering
> for real-time games < add technical content here >"

I'm not interested in watering down the brevity and clarity of the
announcement.  We meet *in person* to discuss such things.


Cheers,                         www.indiegamedesign.com
Brandon Van Every               Seattle, WA


// return an array of 100 packed tuples
temps
  int $[tvar0][2*100]; // what the c function needs
  value $[tvar1]; // one int
  value $[tvar2]; // one tuple
  int $[tvar3] // loop control var
oncePre
eachPre
  $[cvar0]=&($[tvar0][0]);
eachPost
  $[lvar0] = alloc(2*100, 0 /*NB: zero-tagged block*/ );
  for(int $[tvar3]=0;$[tvar3]<100;$[tvar3]++) {
    $[tvar2] = alloc_tuple(2);
    $[tvar1] = Val_int($[cvar0][0+2*$[tvar3]]);
    Store_field($[tvar2],0,$[tvar1]);
    $[tvar1] = Val_int($[cvar0][1]);
    Store_field($[tvar2],1,$[tvar1+2*$[tvar3]]);
    Array_store($[lvar0],$[tvar3],$[tvar0]);
  }
oncePost

-------------------
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-08-12  9:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11  4:45 Brandon J. Van Every
2004-08-11  6:53 ` Diego Olivier Fernandez Pons
2004-08-11 20:29   ` Brandon J. Van Every
2004-08-11 21:22     ` don groves
2004-08-11 21:26       ` don groves
2004-08-12  7:36         ` Brandon J. Van Every
2004-08-12  7:50           ` Sven Luther
2004-08-12  8:28     ` Diego Olivier Fernandez Pons
2004-08-12  9:22       ` Brandon J. Van Every [this message]
2004-08-12  9:28 ` Xavier Leroy
2004-08-12 12:59   ` [Caml-list] OCaml growing pains Brandon J. Van Every
2004-08-12 14:58     ` Mikhail Fedotov
2004-08-12 21:30       ` Brandon J. Van Every
2004-08-13  6:05         ` skaller
2004-08-13  7:07           ` Brandon J. Van Every
2004-08-13  8:52         ` Mikhail Fedotov
     [not found] <OOEALCJCKEBJBIJHCNJDAEFIHGAB.vanevery@indiegamedesign.com>
2004-08-12 12:09 ` [Caml-list] Who controls INRIA mailserv filters? Brandon J. Van Every

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=OOEALCJCKEBJBIJHCNJDKEFFHGAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.com \
    --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;
as well as URLs for NNTP newsgroup(s).