pycplus 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bd13b4d71513629e82bfdc275b30886005d1f0c7958c96562d4f9f8b0703ccc2
-  data.tar.gz: a925d460e45d955bef30bc3fb466b766f8e2aa26867763e70e82b613e8310dcf
+  metadata.gz: 2fde7222ccd4137c44659d5df46a12bc2cb57facbb373c129d54af19596aeb93
+  data.tar.gz: b86597ee3514507775c3a2be65e9fd8ed1f2778be48d276b45b99898e0ba8223
 SHA512:
-  metadata.gz: 5927e705387375c7c05b90029993c51639c0bd523f117a435a7a531a4f9918d54e0feb7c622d049a29b8be2d8f0c239497c7ab9fb1d138214b600dfadf4a958f
-  data.tar.gz: 4deab1e187a588b7e2c19a6449252503c93be7057d785d19ed267956b587be60713e374347fe291b5f9cc34a43930590119244cc54798fb76152296543e153e1
+  metadata.gz: 1437d02dc107e13a85893882db8d325e42d46e62783eeb27c7c58cbf4ce08bc844103e011084a36686ed465fac755bb3e45f96b274e9df4788637fd64ae33bfc
+  data.tar.gz: 03faa5bad0cd3ca3242d64e236995baa1d03337d68fe013d3152e6f2a82d74919c8311cd2d1c1361486a8ff55515134d7cd7c0e3be9931b9f72533160f6adb74

data/README.md

@@ -1,93 +1,3 @@
 # TDP019
 
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.liu.se/andjo858-ip/tdp019.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.liu.se/andjo858-ip/tdp019/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+TODO

data/bin/pycplus

@@ -1,26 +1,65 @@
 #!/usr/bin/env ruby
 # frozen_string_literal: true
 
-require_relative '../lib/lang.rb'
+require 'optparse'
+require_relative '../lib/pcpparse'
 
 
-if ARGV.empty?
-    puts "No arguments provided."
-else
-    arg = ARGV[0]
+# Method to print gem version
+def print_version
+    spec = Gem::Specification.load('../pycplus.gemspec')
+    puts "#{spec.name} version #{spec.version}"
+end
+
+def main
+    # Parse other command-line options using OptionParser
+    options = {}
+    OptionParser.new do |opts|
+
+        opts.banner = "Usage: #{File.basename($PROGRAM_NAME)} [options] filename"
+
+        # version is handled as a special case as it doesn't make sense to use it alongside the other options
+        opts.on("-v", "--version", "Display version information") do
+            print_version
+            exit
+        end
+
+        opts.on("-d", "--debug", "Enable debug mode") do
+            options[:debug] = true
+            print("dhsdhshdshds")
+        end
+    end.parse!
 
-    @lang_parser = MyLang.new
+    # Check if a filename argument is provided
+    if ARGV.empty?
+        puts "Error: No filename or arguments provided."
+        exit 1
+    end
+
+    filename = ARGV.shift
+    @lang_parser = Pycplus.new
 
-    if File.file?(arg)
-        extension = File.extname(arg)
+    # Enable debug mode if specified
+    if options[:debug]
+        @lang_parser.log(true)
+    else
+        @lang_parser.log(false)
+    end
+
+    if File.file?(filename)
+        extension = File.extname(filename)
 
         if extension == ".pcp"
-            @lang_parser.log(false)
-            @lang_parser.parse_file(arg)
+            @lang_parser.parse_file(filename)
         else
-            puts "File is not a .pcp file, make sure to use the correct extension."
+            puts "Error: File is not a .pcp file. Please provide a file with the correct extension."
         end
     else
-        puts "Unable to find file #{arg}"
+        puts "Error: Unable to find file #{filename}"
     end
 end
+
+
+if __FILE__ == $PROGRAM_NAME
+    main
+end

data/lib/nodes.rb

@@ -2,51 +2,38 @@
 
 require_relative 'STL.rb'
 
-# Class to handle scopes when evaluating AST.
 class Scope
-  attr_reader :identifiers,:parent_scope, :non_local_variables
+  attr_reader :identifiers,:parent_scope
   def initialize(parent_scope = nil)
     @identifiers = {}
-    @non_local_variables = []
     @parent_scope = parent_scope
   end
 
-  # Set variable in current scope
   def set_variable(name, op, expression)
-    if @non_local_variables.include?(name)
-      raise NameError, "local identifier #{name} referenced before assignment"
-    end
     if op == '='
       @identifiers[name] = expression
     else
-      unless @identifiers.has_key?(name)
-        raise NameError, "local identifier #{name} referenced before assignment"
-      end
+      id_scope = get_scope(name)
+      @identifiers[name] = get_identifier(name) if id_scope
       if op == '+='
+        @identifiers[name] = 0 if !id_scope
         @identifiers[name] += expression
       else
+        @identifiers[name] = 0 if !id_scope
         @identifiers[name] -= expression
       end
     end
   end
 
-  def set_non_local_variable(name)
-    unless @non_local_variables.include?(name) && is_function(name)
-      @non_local_variables.append(name)
-    end
-  end
-
-  # Get value of identifier in current or parent scope(s) if defined.
   def get_identifier(name)
     scope = get_scope(name)
     if scope
       return scope.identifiers[name]
     else
-      raise NameError,"Identifier #{name} not defined in scope."
+      raise NameError,"Identifier #{name} not defined."
     end
   end
 
-  # Get first scope where identifier is defined.
   def get_scope(name)
     if @identifiers.has_key?(name)
       return self
@@ -55,20 +42,17 @@ class Scope
     end
   end
 
-  # Checks if a identifier is a function.
   def is_function?(name)
     scope = get_scope(name)
     id_value = scope.get_identifier(name) if scope
     return id_value.is_a?(Hash) 
   end
 
-  # Set a function in current scope.
   def set_function(name, block, parameters)
     @identifiers[name] = {:parameters => parameters, :block => block}
   end
 end
 
-
 class BlockNode
   def initialize(statements = nil)
     @block = statements
@@ -118,10 +102,10 @@ class FunctioncallNode
     return result
   end
 
-  def evaluate_block(parameters, block, current_scope, id_scope)
-    new_scope = Scope.new(id_scope)
+  def evaluate_block(parameters, block, scope)
+    new_scope = Scope.new(scope)
     parameters.zip(@arguments).each do |parameter, argument|
-      new_scope.set_variable(parameter, '=', argument.evaluate(current_scope))
+      new_scope.set_variable(parameter, '=', argument.evaluate(scope))
     end
 
     result = block.evaluate(new_scope)
@@ -151,7 +135,7 @@ class FunctioncallNode
       parameters = function[:parameters]
       block = function[:block]
       validate_arguments(parameters)
-      evaluate_block(parameters, block,scope,id_scope)
+      evaluate_block(parameters, block, scope)
     end
   end
 end
@@ -290,12 +274,9 @@ class IdentifierNode < PrimitiveNode
   def evaluate(scope)
     if scope.is_function?(@value)
       raise SyntaxError, "Identifier #{@value} is assigned to a function. Please use correct syntax for function call."
+    else
+      return scope.get_identifier(@value)
     end
-    id_value = scope.get_identifier(@value)
-    unless scope.identifiers.has_key?(@value)
-      scope.set_non_local_variable(@value)
-    end
-    return id_value
   end
 end
 
@@ -306,5 +287,4 @@ class DigitNode < PrimitiveNode
 end
 
 class BoolNode < PrimitiveNode
-end
-
+end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pycplus
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.0
 platform: ruby
 authors:
 - Johannes