程式碼定位、追蹤與修改操作筆記
This article provides a comprehensive guide on how to locate, trace, and modify code without the use of AI. It outlines a workflow for identifying function definitions, finding references, and ensuring safe modifications. The guide emphasizes the importance of using the right tools and methods at each stage of the process.
- ▪The article details a workflow for code modification that does not rely on AI tools.
- ▪It highlights the importance of first narrowing down the search with quick tools before using more precise ones.
- ▪The guide includes specific commands and tools for locating function definitions and references in Swift projects.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3965669) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Hsin-Chieh Cheng Posted on Jun 3 程式碼定位、追蹤與修改操作筆記 #swift #ios #xcode #workflow 程式碼定位、追蹤與修改操作筆記 這份筆記整理一套不用 AI 時也能照著做的工作流程：如何定位函式定義、找引用、追資料流、確認行為，並安全修改檔案。 核心原則 先用最快的工具縮小範圍，再用更精準的工具確認語意。 先找「定義」與「引用」，再讀上下文，不要只看單行。 修改前先確認資料流與呼叫順序，修改後用 git diff、build、test 驗證。 對 Xcode project 管理的 Swift 檔案，新增、刪除、搬移時要注意 .xcodeproj reference。 工具選擇 需求 優先工具 何時使用 快速找文字、函式、變數 rg 第一輪定位，速度最快 看檔案行號與上下文 nl -ba + sed 找到結果後閱讀附近程式 找 Swift 定義、引用、型別 Xcode index / SourceKit-LSP 同名函式、overload、protocol extension 較多時 Swift…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
