Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Klayout version update.
Hi Sir,
as mention before , I am an bumping designer and using Klayout to make some script to do something.
currently , we using 0.28.12 , a little old version.
I knew that your team upudate Klayout to 0.30.3 , and I am under check all of script I maked if that is workable or not.
What my questiion is , I knew that you have make a note and list to shown what gengie been updated or bugfix.
BUT , some of that is hard to line with my script ,
I don't know how to compare my existing scripts and programming with your notes....
Is it possible to shown that more easy to read?
Comments
Hi @jiunnweiyeh,
there is no test or something like this which tells you if scripts are still functional - except testing them.
Usually, all features are backward compatible. Only very rarely, things change in a way that scripts stop working. I think that 0.28.12 is sufficiently compatible with 0.30.3. I am not aware of breaking changes.
Matthias
Hi @Matthias
Is it possilble to shown a list as the release notes , but shown which command corresponds to this update?
such as this one.
Bugfix: Ruby binding - "return" inside block was behaving like "break".
Now, "return" will leave the current function.
For me , the newbie of programming /script coder. that will clearly to understaned which command will been chnage or somethinkg. we need to do modify or not.
of couse , shown as this table will been more readably.
Hi @jiunnweiyeh,
no sorry, that is far too much effort for me. I am still mostly alone on this project. Providing this information is a hell of a work (we are talking about 1000+ functions and methods) and I feel that it's just covering up for users who do not want to establish proper testing for their own software.
By this I mean that someone writing code using KLayout's API should have enough test support built into his own software, that is should be easy to qualify a new KLayout version by simply running the test suite of his own. This is not a good practice for KLayout only, you should adopt this work style whenever you integrate some third party component.
A good example are the DRC and LVS implementations that come with the various open source PDKs. They all come with a test suite which I am using in return to test my one code. So there is even a win-win situation.
Matthias