Updates from cartesianprogramming Toggle Comment Threads | Keyboard Shortcuts

  • cartesianprogramming 05:53 on 2012/05/22 Permalink | Reply  

    TransLucid preamble 

    There are now a number of TransLucid examples available at the TransLucid Web site.
    All of these examples use the declarations found in the preamble.

    http://translucid.web.cse.unsw.edu.au/examples/header.tl

    Advertisements
     
  • cartesianprogramming 05:30 on 2012/05/22 Permalink | Reply  

    Publication archive 

    To help gather the open problems related to implementing TransLucid,
    a publication archive has been prepared. It is available at
    http://plaice.web.cse.unsw.edu.au/archive
    Included in that archive are the collected works of John Plaice,
    Blanca Mancilla and Bill Wadge, along with all of the papers
    presented at the International Symposia on Lucid and
    Intensional Programming
    and the Conferences on
    Distributed Communities on the Web
    .

     
  • cartesianprogramming 05:22 on 2012/05/22 Permalink | Reply  

    The first release of TransLucid is out! 

    It has taken a long time to come, but the first release of TransLucid,
    version 0.1.0, is out. It is available at the following link.
    http://sourceforge.net/projects/translucid/files/TransLucid/0.1.0/tl-0.1.0.tar.bz2/download

     
  • cartesianprogramming 03:22 on 2011/11/22 Permalink | Reply  

    The new C++ 

    The TransLucid interpreter is being written using the new standard C++, called C++11.
    For interesting discussions about C++11, I recommend the http://thenewcpp.wordpress.com blog.
    For a summary of the current C++11 implementation of the GNU gcc compiler suite, go to http://gcc.gnu.org/projects/cxx0x.html

     
  • cartesianprogramming 03:17 on 2011/11/22 Permalink | Reply  

    TransLucid is live and online 

    The TransLucid interpreter is coming alive. It now implements a full functional programming language. It can be used online at http://translucid.web.cse.unsw.edu.au

     
  • cartesianprogramming 09:59 on 2010/09/14 Permalink | Reply  

    Semantics of header entries 

    Since headers are needed for equations to be parsed, and (at least in theory) equations can come from multiple simultaneous sources, there will be a need for multiple simultaneous headers, which should simply be unioned together, no? This means that one should be able to load the same library multiple times and declare the same dimension multiple times, and so on. What is necessary is that everything be consistent, e.g., an operator cannot be defined to have multiple interpretations.

     
    • jarro2783 10:07 on 2010/09/14 Permalink | Reply

      I think this goes with the post 2 down. The header semantics need to be better defined, including the deletion of dimensions, and the parser should be sensitive to time and other context. Currently the header just gets added to and the parser parses by whatever the header says at the time that it was called.

  • cartesianprogramming 04:42 on 2010/09/13 Permalink | Reply  

    Formalization of the interpreter 

    The interpreter needs to be formalized once the operational semantics is finished. This is a necessary step towards writing TransLucid in TransLucid. The key missing parts for writing TL in TL are:

    1. Besfitting
    2. Parsing (a form of bestfitting)
    3. Printing (a form of bestfitting)
    4, Libraries

    We are close on all of these. But nothing is finalized.

     
    • jarro2783 10:05 on 2010/09/14 Permalink | Reply

      1. We need a good algorithm to determine the bestfit equation. The best I can think of would be n^2 because it has to determine for every equation whether it is more specific than every other.
      2. Not sure about how to tackle this still. Some sort of recursive descent thing which mimics spirit could be feasible. I can see that in the future we could even beat spirit, possibly blowing it out of the water. We quite possibly need functions in TL to do this.
      3. String operations are probably required, apart from that it seems trivial.
      4. It seems that we just need some proper semantics. At the moment a library adds equations when it’s loaded. Libraries are currently written in c++, we could allow these to be translucid files too.

      • cartesianprogramming 10:12 on 2010/09/14 Permalink | Reply

        If you store information separately for each variable, then testing applicability is linear in the number of entries for that variable. Among the applicable entries, finding bestfit ones is quadratic in the number of applicable entries.

        This can be improved by using just-in-time ideas. After each modification of the set of equations for a variable, the first time that a demand is made for that variable would force the creation of a finite-state automaton that would be run upon any request for that variable (until, of course, the next modification to the set of equations).

        • cartesianprogramming 10:14 on 2010/09/14 Permalink

          The initial implementation can be done using the linear-quadratic solution. Just-in-time ideas can be kept for future optimization.

        • jarro2783 00:18 on 2010/09/16 Permalink

          what about including priority in that?

  • cartesianprogramming 11:33 on 2010/08/26 Permalink | Reply  

    What are the operators available in tlcore? If we are loading up the integer library, we should provide the operations therein, as in the five operators. Is this done?

     
    • jarro2783 01:29 on 2010/08/27 Permalink | Reply

      I don’t understand the question.
      tlcore has no built in operators, they all come through loading the integer library and declaring things in the header. Are you wanting some of this to be automatic?
      To which five operators are you referring? There are plenty that we could have, all the arithmetic and comparison operators, we could have bitwise operators too. It’s partly a question of how we can implement these with a minimum of typing too.

      • cartesianprogramming 04:08 on 2010/08/27 Permalink | Reply

        I think that there should be a default set of operators. We can always use a flag to turn these on and off. For integers, at the minimum, +, -, *, /, %. For comparison, we have a problem with the angle brackets, we could use ge, gt, le, lt.

    • cartesianprogramming 05:01 on 2010/08/27 Permalink | Reply

      Parsing negative numbers is also problematic if we are not using the intmp interface. I propose that we do the same as in Haskell, and use the tilde (~) to indicate a negative number. That way there will be no confusion between ~3 (negative-three) and -3 (the negation operator applied to three).

    • jarro2783 04:04 on 2010/08/30 Permalink | Reply

      I forgot about the angle brackets. Although only < is a problem. Using tilde is a good idea. I think having a default set of operators is a good idea too. We should come up with a reasonable set of associativities and precedences and allow them to be redefined.

  • cartesianprogramming 11:18 on 2010/08/26 Permalink | Reply  

    Outputtting uuid in tlcore 

    tlcore --uuid
    %%
    x=5;;
    %%
    x;;
    4557f67592cb498fa684d50f5511a65
    intmp<5>

    This is neat, here are a few comments.

    1. The output from the equations section should be separated from the output from the expressions section with a %%.

    2. The uuid “4557f67592cb498fa684d50f5511a65” should read “uuid<4557f67592cb498fa684d50f5511a65>“.

    3. The output from the equations section is not taking into account the –verbose option.

    4. In –verbose mode, we should output equations, demands and expressions as eqn<…>, dem<…> and expr<…>, respectively.

    5. Should there be ;; at the end of each line of output?

    6. Should there be a separator between the input and output? As in a line ?

     
    • jarro2783 11:21 on 2010/08/26 Permalink | Reply

      uuid or uuid … ?
      The rest is easily fixed.

      • cartesianprogramming 11:23 on 2010/08/26 Permalink | Reply

        Problems with angle brackets. Now fixed.

        • jarro2783 11:24 on 2010/08/26 Permalink

          and my reply got broken with the angle brackets too, that doesn’t say what I intended it to.

      • cartesianprogramming 12:01 on 2010/08/26 Permalink | Reply

        The fix looks good. Points 5 and 6 should be tried out. For point 6, that is two dashes on a separate line, to separate the input lines from the output lines. In the reactive mode, there should be two lines with two dashes, before and after each output. If this is too verbose, we can remove it.

  • cartesianprogramming 06:59 on 2010/08/09 Permalink | Reply  

    The “tlcore with demands” and “reactive tlcore” entries have been updated: The ## has been replaced with $$.

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel