|
|
|
|||||
|
For instance, to add some attribute description can enhance the interface signature which support the pre-condition(Require), post-condition(Ensure) or the invariant ... When ice generate the cpp/head files, it also generate the assert conditions. So it can reduce many trivial coding works and make the code more consistant
![]() |
|
||||||
|
Hmm... given that in many cases object state is not expressed in Slice, I'm not sure how this can work. What would for example invariants test, if an Ice object is only defined by an interface, but not by a class with data members?
I guess what Slice could do is to add range check for parameters, i.e. a limited form of pre- and post-conditions. But this would require a much more sophisticated expression evaluator in Slice, especially when it comes to complex data types (e.g., checking for certain values or ranges in a sequence element, which is a member of a struct, which is contained in a dictionary). This could become complicated very quickly, so that in the end Slice is not a specification language anymore, but a rather an implementation language. |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| What feature would you like to see most in Ice? | marc | Comments | 205 | 04-20-2008 03:13 PM |
| Ice.Application feature requests | bartley | Comments | 4 | 02-05-2006 01:56 AM |
| Small C# Feature Request | acbell | Comments | 1 | 04-21-2005 01:12 AM |
| Feature request: Mutex classes | stephan | Comments | 1 | 03-27-2005 03:25 PM |
| platform feature matrix | dlyall | Comments | 0 | 09-02-2004 03:52 PM |