4 Commits

Author	SHA1	Message	Date
Dawn Perchik	045c829223	Fix evaluation of unicode character arrays (char16_t[] and char32_t[]) ... Suppose we have the UTF-16 string: char16_t[] s = u"hello"; Before this patch, evaluating the string in lldb would get: (char16_t [6]) $0 = ([0] = U+0068 u'h', [1] = U+0065 u'e', [2] = U+006c u'l', [3] = U+006c u'l', [4] = U+006f u'o', [5] = U+0000 u'\0') After applying the patch, we now get: (char16_t [6]) $0 = u"hello" Patch from evgeny.leviant@gmail.com Reviewed by: granata.enrico Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D13053 llvm-svn: 248555	2015-09-25 02:16:52 +00:00
Enrico Granata	fa6b278f9c	Add the ability for formatter categories to be bound to one or more languages ... What that does is it restricts formatters in those categories to only match to types coming from "compatible" source languages llvm-svn: 247872	2015-09-17 00:14:50 +00:00
Enrico Granata	419d79189f	Nuke CXXFormatterFunctions.cpp - split the contents of it across different files, so that things are better organized along the C++/ObjC line ... This is preparatory work for moving these formatters into language categories llvm-svn: 246827	2015-09-04 00:33:51 +00:00
Enrico Granata	df7e79e646	Move the functions that FormatManager uses to actually load formatters into their own file ... These are useful helpers over the low-level API of the FormattersContainer, and since we're actually going to start moving formatters into plugins, it makes sense to simplify things llvm-svn: 246612	2015-09-02 01:21:31 +00:00