Skip to main content
16 events
when toggle format what by license comment
Oct 31, 2012 at 11:48 comment added MarkJ The first methodological point should be to look into the risks. I strongly suggest considering the risk that this project is much harder than you think at first, especially if you have never done language translation before. So you should look into the programming side first. These investigations might cause the project to be cancelled or substantially rethought. Worry about planning methodologies later (if ever).
Oct 31, 2012 at 9:20 comment added SK-logic XML is one of the worst possible intermediate representation media one can imagine, especially on an AST level. Please do not do it!
Oct 31, 2012 at 8:57 answer added vainolo timeline score: 0
Oct 31, 2012 at 7:55 answer added Gary timeline score: 0
Oct 30, 2012 at 20:34 comment added Brian The fun part comes when someone calls something within the Java framework that works completely differently (or doesn't exist) in the target language. So, you not only need to write a compiler, but also need to write a framework.
Oct 30, 2012 at 20:23 comment added Jimmy Hoffa @user123 if you haven't looked "into the programming side of things" yet, I would hold up on all the other documentation you're writing and start looking into compiler theory. It sounds like you don't understand the size of the project you're trying to bite off. Here, there be dragons. amazon.com/Compilers-Principles-Techniques-Alfred-Aho/dp/…
Oct 30, 2012 at 18:00 answer added Brian timeline score: 4
Oct 30, 2012 at 16:13 comment added user 123 I have done a lot of reading and i'm writing the plan at the moment i'm up to the methodology section of the plan but I'm just not sure which one to use for a project such as this. Once I've done the methodology section, I do the Risks, Ethics etc sections then i'm going to look more into the programming side of things. :)
Oct 30, 2012 at 16:11 comment added Jimmy Hoffa As Robert Harvey said, some very advanced topics. If you're asking questions on here about these things how confident are you that you have the necessary grasp on compiler theory to really do this correctly? I don't want to discourage you; you could learn a veritable treasure trove trying something like this, but I would suggest a little further study if you are unsure about how to approach the project.
Oct 30, 2012 at 15:56 comment added user 123 He's not sure either :(.
Oct 30, 2012 at 15:54 comment added Robert Harvey What is your friend's opinion?
Oct 30, 2012 at 15:53 comment added user 123 Hi I have to specify the methodology for the project and also document, plan and develop it according to a set methodology, but not sure which one to use, any advice would be great thanks :).
Oct 30, 2012 at 15:42 comment added Robert Harvey You're talking about some fairly advanced topics, on a project of two people, and asking us whether or not you should use agile? Just write the thing.
Oct 30, 2012 at 15:41 history edited gnat CC BY-SA 3.0
spelling, formatting, personal stuff cleanup
Oct 30, 2012 at 15:38 review First posts
Oct 30, 2012 at 15:41
Oct 30, 2012 at 15:22 history asked user 123 CC BY-SA 3.0