SourceForge.net wrote:
> Bugs item #2973536, was opened at 2010-03-19 23:32
> Message generated for change (Tracker Item Submitted) made by nobody
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=480577&aid=2973536&group_id=55394
> 
> Please note that this message will contain a full copy of the comment thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: None
> Group: None
> Status: Open
> Resolution: None
> Priority: 5
> Private: No
> Submitted By: Nobody/Anonymous (nobody)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: Implement preprocessing of source code, remove splash
> 
> Initial Comment:
> In my effort to slim down JXplorer for usage in web browsers, I implemented 
> source code preprocessing. A very simple one, of course.
> 
> How it works:
> 
> - Before compilation, all source files are backed up.
> 
> - Before compilation, all source files are run through a preprocessor script, 
> which comments out part of the source (leading //'s)and replaces files in 
> place.
> 
> - After compilation, original source files are restored back into into place.
> 

Why not make a separate copy with the changes, then build both the program
and the applet?
Overwriting the source and replacing just sounds like trouble.


> - All operations maintain file's modification time stamp.
> 
> This approach has a few advantages: Error/Warning line numbers from the 
> compiler are still valid, an IDE code editor doesn't even see the commented 
> out code. This way, you can still click URLs next to the warning messages, 
> IDE's mini-helpers stay valid.
> 
> How to comment out some code:
> 
> - Put pairs of //#if SOME_FLAG and //#endif on single lines into your code.

Why not just use standard preprocessor directives?

> 
> - Duplicate one of the lines in preprocess.sh and edit it to match your 
> SOME_FLAG.
> 
> For demonstration, usage of the splash screen is commented out.
> 
> 
> BTW.: My Email is still [email protected], still can't log in.
> 
> ----------------------------------------------------------------------
> 
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=480577&aid=2973536&group_id=55394
> 
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Jxplorer-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jxplorer-devel
> 
> 

-- 

  Douglas E. Engert  <[email protected]>
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Jxplorer-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jxplorer-devel

Reply via email to