Hi
I've just found a bug which can you make losing data. I don't know if this bug is know, but I'll post it here.
If you end up your php file with an comment like this
<?php
/*
?>
and you have the class browser refreshing (eg. by hitting F5 or having the class browser on and saving (what will make the class browser to refresh)), devphp will stop working.
It won't crash, but the Php-parser will run into an closed loop and you won't be able to save your data.
I don't know whether this bug affects devphp 2.x
Would be nice if anyone fix it
Greetings Ram3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Another major issue with the class browser is that if you don't completely write out a function heading before the class browser updates, such as when you save a file, flip through your file tabs, etc, the program goes into a loop of death.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I've just found a bug which can you make losing data. I don't know if this bug is know, but I'll post it here.
If you end up your php file with an comment like this
<?php
/*
?>
and you have the class browser refreshing (eg. by hitting F5 or having the class browser on and saving (what will make the class browser to refresh)), devphp will stop working.
It won't crash, but the Php-parser will run into an closed loop and you won't be able to save your data.
I don't know whether this bug affects devphp 2.x
Would be nice if anyone fix it
Greetings Ram3
For coming version 2.0.11 this is fixed. But.. comments should be closed with */ -:)
Sure
I just forgot closing the comments and this made me loose 10 minutes of work :)
Another major issue with the class browser is that if you don't completely write out a function heading before the class browser updates, such as when you save a file, flip through your file tabs, etc, the program goes into a loop of death.