LARP

Bugs and suggestions

You will find herein a list of reported but not yet corrected bugs in LARP, as well as a list of interesting suggestions submitted by LARP users.

  • How to report a bug - instructions on how to submit bug reports to LARP's technical support.
  • Bugs - list of bugs reported to date and yet to be corrected within LARP.
  • Suggestions - list of suggestions reported to date but not implemented yet within LARP.

If you want to inform LARP's technical support of a bug encountered within the software, you may use the bug report system in LARP or send the information directly to LARP's technical support through the Web.


How to report a bug

In spite of all the attention of LARP's author to provide you with robust and bug free software, programming errors or omissions are sometimes overlooked. It is probably the case with LARP, unfortunately.

LARP has an automated report system allowing the user to send bug diagnosis information to technical support by electronic mail. This bug report system is accessible via the top menu, under item Help:

Reporting a bug in LARP

Here are the characteristics of LARP's bug report system:

  • A logging system records in a file all error messages displayed by LARP.
  • If a project file is loaded in LARP when a bug is encountered, a copy of the project file is automatically secured for dispatch to LARP's technical support.
  • If the computer is equipped with an electronic mail agent (for instance, Microsoft® Outlook®), an email can automatically be sent to LARP's technical support team.

When you encounter a problem or bug within LARP, use the Report a bug... command to send all pertinent information to LARP's technical support. If for some reasons you cannot use LARP's automated bug report system, you may send the information directly to LARP's technical support through the Web.


Reported bugs

Here are the bugs reported to date by LARP users, and their status:

Number B1 Opening date 12/08/2004
Priority Low Closing date  
Status Logged LARP version 1.01
Category Program
Description When a pseudo code line is too long, the compiler is not able to process it.
Notes For now, avoid pseudo code lines longer than 251 characters in length. Split longer lines into several shorter ones using the continuation symbol ($).

Number B2 Opening date 15/07/2006
Priority Low Closing date  
Status Logged LARP version 1.01
Category Program
Description The search window does not always find text which is clearly visible in pseudo code.
Notes Checked and confirmed. The bug will be corrected in a future release of LARP.


Reported suggestion

Here are the suggestions and/or improvements reported to date by LARP users, and their status:

Number S1 Opening date 24/10/2005
Priority Medium Closing date 17/12/2007
Status Closed LARP version 3.00
Category Program
Description A debugger should be integrated into the development environment for students to familiarized themselves with such tools.
Notes It's done!