|
|
|
|
(*
|
|
|
|
|
* Copyright (c) 2013 - present Facebook, Inc.
|
|
|
|
|
* All rights reserved.
|
|
|
|
|
*
|
|
|
|
|
* This source code is licensed under the BSD style license found in the
|
|
|
|
|
* LICENSE file in the root directory of this source tree. An additional grant
|
|
|
|
|
* of patent rights can be found in the PATENTS file in the same directory.
|
|
|
|
|
*)
|
|
|
|
|
|
|
|
|
|
open! Utils
|
|
|
|
|
|
|
|
|
|
(** Methods for creating a procdesc from a method or function declaration
|
|
|
|
|
and for resolving a method call and finding the right callee *)
|
|
|
|
|
|
|
|
|
|
(** When the methoc call is MCStatic, means that it is a class method. When it is MCVirtual, it
|
|
|
|
|
means that it is an instance method and that the method to be called will be determined at
|
|
|
|
|
runtime. If it is MCNoVirtual it means that it is an instance method but that the method to be
|
|
|
|
|
called will be determined at compile time *)
|
|
|
|
|
type method_call_type =
|
|
|
|
|
| MCVirtual
|
|
|
|
|
| MCNoVirtual
|
|
|
|
|
| MCStatic
|
|
|
|
|
|
|
|
|
|
val should_add_return_param : Typ.t -> is_objc_method:bool -> bool
|
|
|
|
|
|
|
|
|
|
val create_local_procdesc : Cfg.cfg -> Tenv.t -> CMethod_signature.method_signature ->
|
|
|
|
|
Clang_ast_t.stmt list -> (Pvar.t * Typ.t) list -> bool -> bool
|
|
|
|
|
|
|
|
|
|
val create_external_procdesc : Cfg.cfg -> Procname.t -> bool -> (Typ.t * Typ.t list) option -> unit
|
|
|
|
|
|
Using clang's method resolution if possible
Summary: public
Using clang's method resolution. This means that, in method calls, clang gives you a pointer to the declaration of the method.
In some cases though, clang doesn't find the right method. For example, when it finds a method in a category, we
need to make it into a method in the corresponding class, because that's how we treat categories in Infer. Moreover,
when it finds a method in a protocol, that is not useful for us, since the implementation will be in some class. Finally,
sometimes the call is on an object of type id, in which case clang doesn't know what is the correct declaration. In
those cases, we fall back to what we were doing before of approximating the method resolution. We also refactor
some of the code.
Reviewed By: akotulski
Differential Revision: D2679766
fb-gh-sync-id: b79bb85
9 years ago
|
|
|
val get_objc_method_data : Clang_ast_t.obj_c_message_expr_info ->
|
|
|
|
|
(string * Clang_ast_t.pointer option * method_call_type)
|
|
|
|
|
|
|
|
|
|
val get_class_name_method_call_from_receiver_kind : CContext.t ->
|
|
|
|
|
Clang_ast_t.obj_c_message_expr_info -> (Sil.exp * Typ.t) list -> string
|
Using clang's method resolution if possible
Summary: public
Using clang's method resolution. This means that, in method calls, clang gives you a pointer to the declaration of the method.
In some cases though, clang doesn't find the right method. For example, when it finds a method in a category, we
need to make it into a method in the corresponding class, because that's how we treat categories in Infer. Moreover,
when it finds a method in a protocol, that is not useful for us, since the implementation will be in some class. Finally,
sometimes the call is on an object of type id, in which case clang doesn't know what is the correct declaration. In
those cases, we fall back to what we were doing before of approximating the method resolution. We also refactor
some of the code.
Reviewed By: akotulski
Differential Revision: D2679766
fb-gh-sync-id: b79bb85
9 years ago
|
|
|
|
|
|
|
|
val get_class_name_method_call_from_clang : Tenv.t -> Clang_ast_t.obj_c_message_expr_info ->
|
|
|
|
|
string option
|
|
|
|
|
|
|
|
|
|
val method_signature_of_decl : Tenv.t -> Clang_ast_t.decl -> CModule_type.block_data option ->
|
|
|
|
|
CMethod_signature.method_signature * Clang_ast_t.stmt option * CModule_type.instr_type list
|
|
|
|
|
|
|
|
|
|
val method_signature_of_pointer : Tenv.t -> Clang_ast_t.pointer ->
|
|
|
|
|
CMethod_signature.method_signature option
|
|
|
|
|
|
|
|
|
|
val get_method_name_from_clang : Tenv.t -> CMethod_signature.method_signature option ->
|
Using clang's method resolution if possible
Summary: public
Using clang's method resolution. This means that, in method calls, clang gives you a pointer to the declaration of the method.
In some cases though, clang doesn't find the right method. For example, when it finds a method in a category, we
need to make it into a method in the corresponding class, because that's how we treat categories in Infer. Moreover,
when it finds a method in a protocol, that is not useful for us, since the implementation will be in some class. Finally,
sometimes the call is on an object of type id, in which case clang doesn't know what is the correct declaration. In
those cases, we fall back to what we were doing before of approximating the method resolution. We also refactor
some of the code.
Reviewed By: akotulski
Differential Revision: D2679766
fb-gh-sync-id: b79bb85
9 years ago
|
|
|
CMethod_signature.method_signature option
|
|
|
|
|
|
|
|
|
|
val create_procdesc_with_pointer : CContext.t -> Clang_ast_t.pointer -> string option ->
|
|
|
|
|
string -> Procname.t
|
|
|
|
|
|
|
|
|
|
val get_method_for_frontend_checks : Cfg.cfg -> Cg.t -> Location.t -> Cfg.Procdesc.t
|
|
|
|
|
|
|
|
|
|
val add_default_method_for_class : string -> Clang_ast_t.decl_info -> unit
|
|
|
|
|
|
|
|
|
|
val get_procname_from_cpp_lambda : CContext.t -> Clang_ast_t.decl -> Procname.t
|
