Post Reply 
newRPL: Comments revisited
11-03-2015, 10:01 PM
Post: #5
RE: newRPL: Comments revisited
This is somewhat different from what I assumed. I assumed only @@ comments would end up in the compiled object, whereas @ and @@@ comments would be removed immediately - and therefore just useful when using an external editor. According to your description it depends on a special flag.

Is there a length limit for comment lines?

How are the comments stored internally? Is it a header indicating the type of comment and its size, so it can be "skipped", or are the @, @@, @@@ characters actually stored as part of the comment and thus wasting additional space?

Are comments patchable from outside (that is, no checksums etc.)? This would be desirable to implant version control info, serial numbers, perhaps even fixup data. Is it even possible to change the size of an embedded comment in a binary without invalidating the compiled object?

If comments are patchable, is the system safe when the number of newline characters in the comment changes through patching?

Is it possible for the RPL system to somehow retrieve data from inside comments? If so, build date or version info could be extracted from comments and processed or displayed (instead of putting this in some specially crafted variables).



"Programs are poems for computers."
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
newRPL: Comments revisited - Claudio L. - 11-02-2015, 08:46 PM
RE: newRPL: Comments revisited - rprosperi - 11-03-2015, 01:56 AM
RE: newRPL: Comments revisited - matthiaspaul - 11-03-2015 10:01 PM
RE: newRPL: Comments revisited - rprosperi - 11-03-2015, 10:38 PM
RE: newRPL: Comments revisited - BarryMead - 11-17-2015, 08:35 PM
RE: newRPL: Comments revisited - timofonic - 01-07-2016, 09:05 PM

User(s) browsing this thread: 1 Guest(s)