Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Maklak]

Interestingly, my friend who programs in Python reacted to seeing DF RAWs by trying to convert them to JSON, then being unhappy about tabs not having any meaning His reaction to my hand-written Perl code reading some DF tags (and skipping others) was that this language is weird and DF should use JSON instead, so the RAWs can be easily read into a nested hash with one command. My answer was that I'd still need to manually walk that hash (and know it's structure) to do anything useful with it.

He can write in Python one-liners that are pretty obfuscated. For example this code to compute xor from 0 to n:
def rozwiazanie_najszybsze(t):
     n=len(t)+1
    return reduce(int.__xor__,t,0)^[0,n^1,1,n][n&3] 

In my second job, the boss loved perl and some of his subordinates strongly preferred Python. My conclusion was that the languages are pretty equivalent and the choice between them is mostly a matter of having more experience in one or the other.

Personally I use Perl, but constantly bump into some gotchas or just do things by trial, error and print until they work. The lack of { } in Python is a deal-breaker for me, but I sometimes wonder if the grass is greener on the Ruby side of things.

[da_nang]

* da_nang reads latest replies.

* da_nang is hugging GSON tightly.

Spoiler: JsonSerializer (click to show/hide)

Code: [Select]

import com.google.gson.Gson;
import com.google.gson.reflect.TypeToken;

/**
 * Class providing generic static methods of serializing Json formattable objects.
 * @param <T>
 */
public class JsonSerializer<T> {

private static Gson gson = new Gson();

/**
* Formats object to a Json formatted string
* @param obj - generic object to format
* @return Json formatted string
*/
public static <T> String toJsonString(T obj) {

return gson.toJson(obj, new TypeToken<T>(){}.getType());
}

/**
* Generates generic object from Json formatted string
* @param type - Type token to work around possible generic outer types.
* @param json - Json formatted string
* @return generic object
*/
public static <T> T fromJsonString(TypeToken<T> type, String json) {
return gson.fromJson(json, type.getType());
}
}

Spoiler: JsonIO (click to show/hide)

Code: [Select]

import java.io.BufferedReader;
import java.io.BufferedWriter;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.lang.reflect.Type;
import java.nio.charset.Charset;
import java.nio.file.Files;
import java.nio.file.Path;

import com.google.gson.JsonParseException;
import com.google.gson.JsonSyntaxException;
import com.google.gson.reflect.TypeToken;

public class JsonIO<T> {

/**
* Exports any given object that is serializable by Gson to a given file.
* @param obj - the object to export
* @param file - the file to which the the object is exported.
* @throws IOException
*/
public static <T> void exportJson(T obj, Path file) throws IOException {
if (obj == null || file == null) throw new IllegalArgumentException("Parameters can't be null");
String output = JsonSerializer.toJsonString(obj);
export(file, output);
}


/**
* Imports any given object that is serializable by Gson from a given file.
* @param type - Type token required to know which type to deserialize. Use anonymous class as the regular constructor is not visible.
* @param file - file from which the object is imported.
* @returns the imported file, null if the Json string can't be parsed.
* @throws IOException
*/
public static <T> T importJson(TypeToken<T> type, Path file) throws IOException {
if (file == null) throw new IllegalArgumentException("Parameter can't be null");
String input = importString(file);
T obj = null;
try {
obj = JsonSerializer.fromJsonString(type, input);
}
catch (JsonParseException e) {
return obj;
}
return obj;
}

private static void export(Path file, String output)
throws IOException {
if (Files.notExists(file.getParent())) {
Files.createDirectories(file.getParent());
}
if (Files.notExists(file)) {
Files.createFile(file);
}

write(output, file);
}

private static String importString(Path file) throws FileNotFoundException,
IOException {
if (Files.notExists(file)) {
throw new FileNotFoundException("File doesn't exist!");
}
String input = read(file);
return input;
}

private static void write(String output, Path filePath) throws IOException {
BufferedWriter writer = Files.newBufferedWriter(filePath, Charset.defaultCharset());

try {
writer.write(output, 0, output.length());
}
finally {
writer.close();
}
}

private static String read(Path filePath) throws IOException {
BufferedReader reader = Files.newBufferedReader(filePath, Charset.defaultCharset());
StringBuilder input = new StringBuilder();
try {
while(reader.ready()) {
input.append(reader.readLine());
}
}
finally {
reader.close();
}
return input.toString();
}
}

[Levi]

The lack of { } in Python is a deal-breaker for me, but I sometimes wonder if the grass is greener on the Ruby side of things.

I like python, but using indents to denote scope was the dumbest idea ever.  I'm pretty sure its the reason why there are no multiline lambda's in python, and why the web frameworks don't let you embed python into html.  Whenever I use python instead of ruby the one thing I really miss having is multiline lambdas.

[Parsely]

PTW because going to school to become a programmer.

[MrWillsauce]

Am I the only person who decided to learn python because of Hulk Hogan?

[MagmaMcFry]

Why would you learn Python because of Hulk Hogan?

[MrWillsauce]

Because of his 24-inch pythons.

[Parsely]

Duh.

[Gatleos]

Spoiler (click to show/hide)

Why do I do this to myself? I get the brilliant idea of making a program to save myself time, then realize 5 hours into fiddling with linker settings and mashing ui bugs that I've wasted more time making the program than I'll ever save by using it.

C++ makes you a masochist I guess.

[MagmaMcFry]

Congrats, you're a programmer!

[cerapa]

Like most things, xkcd has a comic about it:

[miauw62]

Spoiler (click to show/hide)

Why do I do this to myself? I get the brilliant idea of making a program to save myself time, then realize 5 hours into fiddling with linker settings and mashing ui bugs that I've wasted more time making the program than I'll ever save by using it.

C++ makes you a masochist I guess.

Distribute the project, save the time of a lot of people?

[MagmaMcFry]

I'm pretty sure xkcd has at least five comics about exactly this topic, including two graphs and a table.

[miauw62]

I'm pretty sure xkcd has at least five comics about exactly this topic, including two graphs and a table.

Isn't that true about everything?

[Gatleos]

Distribute the project, save the time of a lot of people?

I was thinking about doing that. It depends on how useful it ends up being. The only reason I'm making it is because I couldn't find anything like it on the internet. It's a sprite animation editor; there are plenty of programs that call themselves that, but they're also bloated with features and are trying to be paint programs.

I didn't want a pixel art paint program, I just wanted a quick and intuitive sprite animation editor. What this program does is load and save a tiny binary file format I made to interface with a sprite animation class (which I also made). It's just a quick way to take an image file, specify an animation from it, and display it onscreen after loading it in another program. Without a huge bloated framework I have to graft onto my existing codebase.