Revision: 15515
Author:   [email protected]
Date:     Fri Jul  5 04:35:01 2013
Log:      Edited wiki page Source through web user interface.
http://code.google.com/p/v8/source/detail?r=15515

Modified:
 /wiki/Source.wiki

=======================================
--- /wiki/Source.wiki   Fri Jul  5 04:32:57 2013
+++ /wiki/Source.wiki   Fri Jul  5 04:35:01 2013
@@ -33,7 +33,7 @@

 == V8 public API compatibility ==

-V8 public API (basically the files under include/ directory) may change over time. New types/methods may be added without breaking existing functionality. When we decide that want to drop some existing class/methods, we first mark it with [https://code.google.com/p/chromium/codesearch#search/&q=V8_DEPRECATED&sq=package:chromium&type=cs V8_DEPRECATED] macro which will cause compile time warnings when the deprecated methods are called by the embedder. We keep deprecated method for one branch and then remove it. E.g. if v8::CpuProfiler::FindCpuProfile was plain non deprecated in 3.17 branch, marked as V8_DEPRECATED in 3.18, it may well be removed in 3.19 branch. +V8 public API (basically the files under include/ directory) may change over time. New types/methods may be added without breaking existing functionality. When we decide that want to drop some existing class/methods, we first mark it with [https://code.google.com/p/chromium/codesearch#search/&q=V8_DEPRECATED&sq=package:chromium&type=cs V8_DEPRECATED] macro which will cause compile time warnings when the deprecated methods are called by the embedder. We keep deprecated method for one branch and then remove it. E.g. if ''v8::CpuProfiler::FindCpuProfile'' was plain non deprecated in ''3.17'' branch, marked as ''V8_DEPRECATED'' in ''3.18'', it may well be removed in ''3.19'' branch.


 == GUI and IDE Access ==

--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to