Posts Comments

Home > Programming > Java > Introduction to JR programming language

Introduction to JR programming language

January 30, 2010 By 18 Comments

6. Conclusion

So, we’ve now discover the main concepts of the JR programming language. Like you have see in this article, this programming language enable to make easier the use of concurrent programming concepts.

I hope that this article has been useful to you to discover the JR Programming Language, and why not, to learn and use this language.

Related posts:

  1. Monitor programming in JR
  2. Asynchronous Message Passing in JR
  3. Rendezvous, concurrency method, in JR
  4. Java Concurrency – Part 1 : Threads
  5. JR Virtual machines

Pages: 1 2 3 4

Filed Under: Java Tagged With: ,
  • http://www.squidoo.com/portlandphotoboothrental2 Nicolas Bohinc

    Thanks for this excellent blog.

  • http://www.squidoo.com/portlandphotoboothrental2 Nicolas Bohinc

    Thanks for this excellent blog.

  • Alexandre Jaquet

    I just found your article after discovering the existence of JR (We learned SR in the past) ;-)

  • Alexandre Jaquet

    I just found your article after discovering the existence of JR (We learned SR in the past) ;-)

  • Steve

    Not sure I see the point: you created a new syntax just to encapsulate new Thread(…).start().

    What’s the gain?

    • Baptiste Wicht

      It’s not me that created the syntax.

      The gain is that for almost every principle of concurrent programming, you have facilities to develop with them. It’s really easy to use semaphores, monitors, message passing, rendezvous, …

      Effectively, you can all the things of JR in Java, but it’s a lot more cleaner with JR.

      • Steve

        “It’s a lot more cleaner in Java”? Then why create JR?

        Besides, in my experience, the difficulty is precisely semaphores, monitors, etc… Creating threads is trivial, so I really don’t see the point in creating a language just for that purpose…

        • Baptiste Wicht

          What I wanted to say it’s that it’s cleaner in JR. Sorry for the error.

          There is not only facilities to create process but also to use semaphores and monitors and to use asychronous message passing and rendezvous. You can also make distributed programs.

          I think it’s good to have. But i’ll not use JR in my real projects

  • Steve

    Not sure I see the point: you created a new syntax just to encapsulate new Thread(…).start().

    What’s the gain?

    • Baptiste Wicht

      It’s not me that created the syntax.

      The gain is that for almost every principle of concurrent programming, you have facilities to develop with them. It’s really easy to use semaphores, monitors, message passing, rendezvous, …

      Effectively, you can all the things of JR in Java, but it’s a lot more cleaner with JR.

      • Steve

        “It’s a lot more cleaner in Java”? Then why create JR?

        Besides, in my experience, the difficulty is precisely semaphores, monitors, etc… Creating threads is trivial, so I really don’t see the point in creating a language just for that purpose…

        • Baptiste Wicht

          What I wanted to say it’s that it’s cleaner in JR. Sorry for the error.

          There is not only facilities to create process but also to use semaphores and monitors and to use asychronous message passing and rendezvous. You can also make distributed programs.

          I think it’s good to have. But i’ll not use JR in my real projects

  • Dontell

    You can write it almost as clean in Java now using static imports:
    for(final int id : sequence(0, 24)) process(new Runnable(){ @Override public void run(){
    System.out.println(“Hello World from thread ” + id);
    }});

    The annoying Runnable boiler plate will soon (“soon”) be replaced by something like
    for(final int id : sequence(0, 24)) process(#(){
    System.out.println(“Hello World from thread ” + id);
    });

    Whenever a new language comes up with “much cleaner syntax” it’s mostly only a trick of comparing apples (some marginal syntax sugar) with oranges (java code without proper static util methods).
    In the end, if you know what to do, you can get the same clarity in java (admitedly for functions only as soon as JDK7 will be out).

    The Java syntax isn’t perfect (and I’m no Java Zealot or something) but I have yet to see a language that is really a noteworthy potential successor.

    • Baptiste Wicht

      Thanks for the reply !

      Effectively, you can do a lot of JR very clean in Java. But if you watch the other articles I wrote about JR, you can see that JR make more than simplify only the creation of processes. You can easily create monitors, function pointers, make asynchronous message passing, rendezvous and even create several virtual machines and make distributed programming.

      But I don’t think JR is a language to replace Java, but it’s a very good language to learn concurrent programming. Personally, I didn’t use this language for my projects, I always use Java. We use JR at school. JR is not installed on a lot of machine, so it’s not easy to distribute that kind of programs.

  • Dontell

    You can write it almost as clean in Java now using static imports:
    for(final int id : sequence(0, 24)) process(new Runnable(){ @Override public void run(){
    System.out.println(“Hello World from thread ” + id);
    }});

    The annoying Runnable boiler plate will soon (“soon”) be replaced by something like
    for(final int id : sequence(0, 24)) process(#(){
    System.out.println(“Hello World from thread ” + id);
    });

    Whenever a new language comes up with “much cleaner syntax” it’s mostly only a trick of comparing apples (some marginal syntax sugar) with oranges (java code without proper static util methods).
    In the end, if you know what to do, you can get the same clarity in java (admitedly for functions only as soon as JDK7 will be out).

    The Java syntax isn’t perfect (and I’m no Java Zealot or something) but I have yet to see a language that is really a noteworthy potential successor.

    • Baptiste Wicht

      Thanks for the reply !

      Effectively, you can do a lot of JR very clean in Java. But if you watch the other articles I wrote about JR, you can see that JR make more than simplify only the creation of processes. You can easily create monitors, function pointers, make asynchronous message passing, rendezvous and even create several virtual machines and make distributed programming.

      But I don’t think JR is a language to replace Java, but it’s a very good language to learn concurrent programming. Personally, I didn’t use this language for my projects, I always use Java. We use JR at school. JR is not installed on a lot of machine, so it’s not easy to distribute that kind of programs.

  • http://www.aryol.com.tr prefabrik

    very qualified post. I’m new for JR programming language and your post about the introduction of it helps me a lot. thanks for your effort.

  • Anonymous

    This is good blog about JR programming language. JR programs are based on Java and again translated into accepted Java programs. The JR run-time support arrangement is aswell based on standard Java.

    toshiba coupon codes