search for: _changes

Hello all. I am looking for some feedback on an implementation. I''m writing a plugin that will log all model changes. I do not want to have to add a line a code for this functionality every time I create a model. Instead I create a table with the name <model>_changes. The basic stuff was easy: base.after_create {|model| model.log_create if model.has_backup_table? } **also log on before_update and before_destroy What I''m curious about is the habtm relationships. I wanted to keep track of when this changes as well. An example woul...

...*_Advantages_ *There are advantages that the atoms within a safe section could just be allocated in the output file which means better output file layout, and Better performance! This would also result in more atoms getting gc'ed. a) looking at profile information b) taking a order file *_Changes needed in the assembler_ *a) add an additional flag in the section for people writing assembly code, to mark a section safe or unsafe. * **_Changes needed in lld_ *a) Read the safe section if its present in the object file b) Tie atoms together within a section if the section is not safe * *Than...