> What this means is the Emacs adheres to the Sun guidelines BY
> DEFAULT. So
> what your complaint?
I have to warn that I executed the following command:
M-x auto-fill-mode
That may not be a correct way to go.
The maximum size of the string is 72 characters (in case if I want to print
code with line numbers).
>From Sun document:
Wrapping Lines
When an expression will not fit on a single line, break it according to
these general principles:
* Break after a comma.
* Break before an operator.
* Prefer higher-level breaks to lower-level breaks.
* Align the new line with the beginning of the expression at the same level
on the previous
line.
* If the above rules lead to confusing code or to code that's squished up
against the right
margin, just indent 8 spaces instead.
Here is an example 1 of the code I use:
/*
* Read ASCII file (MOMap file format) for to assign
* Multipliers.
*/
if (importConfig.getMultiplierOption().equals(
ImportConfig.MO_FILE)) {
FileReader fr;
try {
fr = new FileReader(
importConfig.getMultiplierOptionFile());
} catch (FileNotFoundException e) {
importConfig.log(ImportMF.IMF_002, new Object[] {
importConfig.getMultiplierOptionFile()});
throw new ResourceNotFoundException(
"ASCII file in the MOMap format "
+ "to assing multipliers "
+ "is not found. File name is "
+ importConfig.getMultiplierOptionFile()
+ ".", this, e);
}
Here is an example 2 of the code:
/**
* .
*
* @param fieldsDeviceBase Keys are the fields (String[]). Values
* are DeviceBase objects.
*/
protected void generateChannelSources(Map fieldsDeviceBase)
throws RecordsGroupException {
/* create ChannelSource, ChannelRecording objects */
String[] fields;
...
}
The biggest complaint I have is that emacs will always create a code like
this:
methodName(new Object(
"value",
"value"));
while I need it to be
methodName(new Object(
"value",
"value"));
You can also find that I prefer to use 8 spaces, because most of the
identifiers are very long, thus nested indentation does not work well in the
72 characters rantge (80 does not help a lot).
