search for: _wrap

With the new "stamp" rules for running SWIG, things don't seem to get rebuilt when I expect them to, e.g.: olly at ixion:~/svn/xapian/xapian-bindings/python $ make modern/xapian_wrap.cc make: Nothing to be done for `modern/xapian_wrap.cc'. olly at ixion:~/svn/xapian/xapian-bindings/python $ ls -l modern/xapian_wrap.cc ls: modern/xapian_wrap.cc: No such file or directory Problem being that the "stamp" file already exists. This used to work before though... Cheer...

...ore.py", line 177, in svn_pool_create return Pool(parent_pool) File "/var/lib/python-support/python2.4/libsvn/core.py", line 1080, in svn_pool_create return apply(_core.svn_pool_create, args) File "/var/lib/python-support/python2.4/libsvn/core.py", line 3103, in _wrap obj.set_parent_pool(self) File "/var/lib/python-support/python2.4/libsvn/core.py", line 2994, in set_parent_pool self._parent_pool = parent_pool or application_pool File "/var/lib/python-support/python2.4/libsvn/core.py", line 2982, in <lambda> __setattr__...

...t;, line 177, in svn_pool_create return Pool(parent_pool) File "/var/lib/python-support/python2.4/libsvn/core.py", line 1080, in svn_pool_create return apply(_core.svn_pool_create, args) File "/var/lib/python-support/python2.4/libsvn/core.py", line 3103, in _wrap obj.set_parent_pool(self) File "/var/lib/python-support/python2.4/libsvn/core.py", line 2994, in set_parent_pool self._parent_pool = parent_pool or application_pool File "/var/lib/python-support/python2.4/libsvn/core.py", line 2982, in <lambda> __s...

...4.to_int c1)); + Bytes.unsafe_set b 2 (Char.unsafe_chr (Int64.to_int c2)); + Bytes.unsafe_set b 3 (Char.unsafe_chr (Int64.to_int c3)); + Bytes.to_string b + +type wrap_break_t = WrapEOS | WrapSpace | WrapNL + +let rec wrap ?(chan = stdout) ?(indent = 0) str = + let len = String.length str in + _wrap chan indent 0 0 len str + +and _wrap chan indent column i len str = + if i < len then ( + let (j, break) = _wrap_find_next_break i len str in + let next_column = + if column + (j-i) >= 76 then ( + output_char chan '\n'; + output_spaces chan indent; + i...

OCaml 4.02 introduced the 'bytes' type, a mutable string intended to replace the existing 'string' type for those cases where the byte array can be mutated. In future the 'string' type will become immutable. This is not the default now, but it can be forced using the '-safe-string' compile option. I tested this on Fedora 24 (OCaml 4.02) & RHEL 7 (OCaml 4.01).

This is just the utilities part of the patch series from: https://www.redhat.com/archives/libguestfs/2017-June/msg00103.html I believe this addresses everything raised in comments on that patch series. Rich.

This turned out to be rather more involved than I thought. We have lots of utility functions, spread all over the repository, with not a lot of structure. This moves many of them under common/ and structures them so there are clear dependencies. This doesn't complete the job by any means. Other items I had on my to-do list for this change were: - Split up mllib/common_utils into: -

This is a combination of: https://www.redhat.com/archives/libguestfs/2017-June/msg00046.html [PATCH 00/12] Refactor utility functions. plus: https://www.redhat.com/archives/libguestfs/2017-June/msg00023.html [PATCH v3 00/19] Allow APIs to be implemented in OCaml. with the second patches rebased on top of the utility refactoring, and some other adjustments and extensions. This passes

v5: https://www.redhat.com/archives/libguestfs/2017-June/msg00065.html Since v5, this now implements inspection almost completely for Linux and Windows guests. Rich.

v7 was: https://www.redhat.com/archives/libguestfs/2017-June/msg00169.html https://www.redhat.com/archives/libguestfs/2017-June/msg00184.html I believe this addresses all comments received so far. Also it now passes a test where I compared about 100 disk images processed with old and new virt-inspector binaries. The output is identical in all cases except one which is caused by a bug in blkid